Testing the Cloud – Top 3 Implications for QA and Software Testing with a Cloud Based Architecture

Cloud computing is the single largest trend in IT deployment today, touted to provide benefits to businesses, ranging from reduced ownership and maintenance costs to device and location independence. But what is cloud computing and what are the issues involved with testing it?

This paper briefly introduces cloud computing before going on to discuss the main benefits and concerns of implementing cloud architectures. The paper then explores how through thorough testing these concerns can be addressed and the potential benefits can be realized.

How to determine the ROI of finding and fixing bugs by using software test automation

Every software application, website release or upgrade is a critical interface with customers. Applications with low quality are easily left for another as there are many alternatives available. If you skimp on quality, you are skimping on your business. There are many ways to measure software quality – but what is the “cost” of quality and more importantly what is the cost for lack of quality. In this white paper we develop a model to calculate how testing pays for itself with lower overall development costs, and in particular by using test automation.

Using SilkTest for Test Automation Dos & Don'ts

Borland SilkTest is one of the most popular tools in software test automation. SilkTest uses a scripting language called 4Test, so using the tool beyond simple recording requires programming skill and experience, especially when designing scripts that are efficient and easy to maintain for testing enterprise applications, which often run on multiple platforms. In this white paper, we'll present a general framework when using SilkTest to do automation testing.

Transforming LoadRunner Data into Information and Action

Today's online web applications need to deliver high efficiency while supporting thousands of users simultaneously. Rather than going live and hoping for the best, HP’s LoadRunner can simulate hundreds or thousands of concurrent usersAfter execution of script, LoadRunner generate graphs and reports to analyze and assess the performance of the application under various load scenarios. hen go beyond the standard reports or detailed analysis, accessing LoadRunner data is cumbersome. rending analysis or results verification requires extraction of raw data from LoadRunner’s results files. But it’s worth it as this allows for greater in-depth analysis which can lead to easier identification of performance bottlenecks and benchmarking for improvements over time.

New Strategies for Testing Agile Developed Software

In the old days with Waterfall development, we figured out what to build; designed, wrote code; tested; and deployed. Testing was usually done late and often separate from development activities. This was often unavoidable because the application was not ready to test. But this led to a lot of problems down the road such as...With agile development, we see progress early, and we can deliver at least something by the original deadline, but to we need adapt the traditional testing model to agile development and compress the testing cycles while continually increasing the quality of the software under test. To do that, there are 3 key activities including...

Defining Quality of Web-based Applications in Today's SaaS World

This paper presents a new framework for measuring the quality of web-based software applications. In the past, companies used to do a software product release by shipping a new CD with an accompanying manual. Today, with Web 2.0 technologies and Software as a Service (SaaS) business models, software delivery is entirely different; it is simply released online. Therefore, new research relating to software quality must let go of some traditional measurement methods and take on newer methods based on providing a service rather than a product. This paper discusses which older measurements now have less validity and provides a framework for newer measurements that can be used to determine and quantify the quality of web-based software applications.

10 Important Lessons Learned in Software Test Automation

Test automation is a critical regression activity in software development projects with short development cycles. As features build up from iteration to iteration and release cycles grow ever shorter, the time required to regression test can expand geometrically. In these circumstances, automation is often viewed as the magic bullet for survival. However, for a variety of reasons, automation projects often fail. Through XBOSoft's years of experience working on countless automation projects, we've come up with a list of 10 key "lessons learned" that we believe if followed, can significantly improve your chances of automation success.

To Be (Automated) or Not To Be (Manual): A Dilemma for Small Development Shops?

Automated software testing has long been an integral part of big software development organizations but is often thought to be too expensive or difficult for smaller companies. In many cases, automation has a proven track record in reducing the costs of testing, increasing test coverage and effectiveness, and shortening testing cycles. There are also various intangible benefits associated with automation such as reaching the market faster and improving tester moral (and productivity) through the elimination of tedious tasks.

Improving QA and Development Cooperation for Higher Software Quality

QA teams are often pushed to the final hour, testing features with altered specifications that no one fully understands. How does QA support creativity and satisfy clients (developers, product managers, end users) but also manage product quality? Here are some practical thoughts: