<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Tape on Scholion</title><link>https://scholion.thluiz.com/tags/tape/</link><description>Recent content in Tape on Scholion</description><generator>Hugo -- gohugo.io</generator><language>pt-BR</language><copyright>© 2026</copyright><lastBuildDate>Sat, 02 Jan 2016 11:55:23 -0300</lastBuildDate><atom:link href="https://scholion.thluiz.com/tags/tape/index.xml" rel="self" type="application/rss+xml"/><item><title>My node test strategy</title><link>https://scholion.thluiz.com/notes/my-node-test-strategy/</link><pubDate>Sat, 02 Jan 2016 11:55:23 -0300</pubDate><guid>https://scholion.thluiz.com/notes/my-node-test-strategy/</guid><description>The author outlines a Node testing workflow built around automation, tape and tap, proxyquire, sinon, JSCS, and Travis, with emphasis on easy setup, resettable tests, and coverage.</description></item></channel></rss>