Tutorials and resources on how to apply test automation in software testing
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.
As cloud computing dives deeply into its latest trend, the proliferation of instances of mobile device access, testing the explosive numbers of new applications could be an obstacle to speedy deployment. Automated testing on the cloud is the answer to that roadblock. This article discusses how to add grid computing and peer-to-peer collaboration functionality to make automated testing on the cloud more effective. It also provides an example of a real-world system and scenario.
Testing continues to represent the single largest cost associated with the development of sophisticated, software intensive, military systems. A reduction in overall testing cost will save billions of dollars over the lifecycle of tactical software systems. Such savings can only be achieved if the concept of testing begins very early in the development process, improving synergy throughout the development and testing communities.
This blog post presents a excellent causal loop diagram on acceptance testing automation and then discusses all the factors that make it difficult to automate well acceptance tests.
Copyright © 2009-2024 Software Testing Magazine by Martinig & Associates