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.
Software Testing Articles: Load Testing, Unit Testing, Functional Testing, Performance Testing, Agile Testing, DevOps
This article explains how to use Arquillian to test a web UI of the application you are building. The mission of the Arquillian project is to provide a simple test harness that abstracts away all container lifecycle and deployment from the test logic so developers can easily produce a broad range of integration tests for their enterprise Java applications. This article exercises the following tools: Arquillian, Arquillian Drone, ShrinkWrap Maven Resolver and Selenium.
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.
As a software testing consultant and musician, I meet a lot of skilled testers who do amazing work. Through experience and a lot of trial and error, they have developed skills they can’t easily explain. Unfortunately, with software testing, there aren’t as many obvious avenues for skill development as there are for musicians. Many software testers don’t realize that there are learnable exploratory testing skills they can develop to help them become even more valuable to software development teams.
This article discusses how to build a portfolio of scenarios for load testing automation. You have rarely only a single scenario to test, so you have to decide which scenarios to include in your test plans. Criticality, frequency, difficulty and verifiability are the four key factors that should be considered to determine the scenarios to automate.