Tutorials and resources on how to apply test automation in software testing
In those days where software tests are integrated in continuous integration cycles, it is a necessity that they run in a minimized amount of time. This article explains how through controlled memory usage, increased parallelism, transactional factory invocation, pragmatically judicious test refactoring and a few miscellaneous extras, it was possible to reduce the time needed to run the tests of a ruby on rails application in continuous-integration environments by a factor of ten.
In this blog post, Adrian Smith discusses 7 pitfalls of automating software testing. The seven sins are over indulging on propriety testing tools, too lazy to setup CI server to execute tests, loving the UI so much that all tests are executed through the UI, jealously creating tests and not collaborating, frustration with fragile tests that break intermittently, thinking automated tests will replace all manual testing, too much automated testing not matched to defined system quality.
This video explains the basic differences between different flavors of functional software testing tools. It proposes a selection roadmap and identifies the best vendors for each scenario. It provides pricing info and recommendations on negotiations.
Have you visited the treasures of Visual Studio Menu bar tools | Options | Test Tools lately? The options to enable disable prompts on creating, editing, deleting or running manual/automated tests can be controller from here. The default test project language and default test types created on a new test project creation could be selected/unselected from here.
This article by Adam Goucher identifies a handful of heuristics that apply to software testing automation. While not an exhaustive set, it is a useful one, and it will put you on the path to identifying and collecting your own set of automation heuristics. Heuristics are used in testing as rules of thumb or prompts for solving a particular problem or class of problems.
Dealing with dependencies is the most challenging aspect of test-driven development (TDD). Mocks and stubs are created to isolate the behavior we would like to test. The article “The Art of Mocking” is a good introduction on this topic. Creating all these testing classes by hand can lead to troubles: sometimes developers duplicate these classes and other times the mocks and stubs become more complicated than the code.
This short tutorial presents a basic introduction to HP LoadRunner automated load testing tool. You will learn how to generate scripts with the Virtual User Generator, design and run a load test in the Controller and analyze the test results.
