Monthly Archives: January 2011

Software Testing is Not Just Debugging

 

Software testing is more than just finding errors in software source code. It serves more complex function in software development than just unearthing script errors. Although software test is described as the process of executing a system with the purpose of finding defects it is more involved in ensuring software’s reliability and determining if it meets the required outcome. It also greatly deals with software’s verification and validation.

One primary purpose of software testing is to evaluate the capabilities or attributes of software’s capability to satisfactorily meet the standards and customer requirements. But one has to remember that software test is not an absolute measure of quality. Testers’ job is to test not to create therefore it is the responsibility of software developer to build a quality software for the testers to perform a quality test on a quality program.

The function of a tester is to point out the bugs and weaknesses of the software it is, again, up to developers to act upon it. Testing can never completely establish the correctness of computer software it simply provide a criticism or comparison of the product to the existing standards, specifications and user requirements.

[...]

Read More:

http://technology.ezinemark.com/software-testing-is-not-just-debugging-4eb0652f2af.html

Did you like this? Share it:

Software Testing Methods

 

Any good software testing services is partly intuitive, but largely methodical. A software testing team follows the steps of software testing life cycle and helps in delivering software project that correct, complete, secure and with quality desired. Software testing practices is not a standalone activity. It is highly dependent on development activity and thus both development phase and testing activities draws heavily from each other. Testing of the software being developed starts with the initial stage of software coding. This enables the quality software tester team to set up the testing environment and configuration that will be required for the delivery of bug free project. Both the development and testing team involved in the design and development of software product or service communicate and understand the problems and concerns that might hamper the success of the project.

Software testing is largely divided into Black-box testing and White-box testing services.

Both these services cater to two different aspects of testing. While the Black-box testing refers to external view of text object the White-box testing is an internal view of the item in discussion. In fact White-box testing and Black-box testing are terms associated with point of view a test case is designed by a tester. Let us discuss the major types of White-box testing that is available and used by testers.

[...]

Read More:

http://technology.ezinemark.com/software-testing-methods-17173085f65.html

Did you like this? Share it:

Growing focus on independent software testing

 

Recent IT outages such as the DBS ATM shutdown and United Airlines Web site erroneously selling US$20 tickets are clear evidence of the serious consequences that software failures can bring along, said Ritendra Banerjee, senior vice president of Maveric Systems, a company that performs software testing.

In a phone interview with ZDNet Asia, Banerjee explained that an increasing number of companies are putting in the extra investment for such testing. Reasons range from preventing large-scale failures to meeting compliance, to simply ensuring that the large investments in technology and software can function and generate returns for the business.

"Lapses can have serious impact on businesses, and these are the companies that rely on thousands of applications to monetize the product for them," he said.

In a recent survey commissioned by the firm, 75 percent of IT executives in Indonesia said software testing plays a "very important" role in their businesses, while the rest said it was "important".

40 percent felt that budget-related issues were the main constraints to software testing, while 20 percent cited the inability to demonstrate return on investment (ROI).

[...]

Read More:

http://www.zdnetasia.com/growing-focus-on-independent-software-testing-62205000.htm

Did you like this? Share it:

Growing focus on independent software testing

 

Recent IT outages such as the DBS ATM shutdown and United Airlines Web site erroneously selling US$20 tickets are clear evidence of the serious consequences that software failures can bring along, said Ritendra Banerjee, senior vice president of Maveric Systems, a company that performs software testing.

In a phone interview with ZDNet Asia, Banerjee explained that an increasing number of companies are putting in the extra investment for such testing. Reasons range from preventing large-scale failures to meeting compliance, to simply ensuring that the large investments in technology and software can function and generate returns for the business.

"Lapses can have serious impact on businesses, and these are the companies that rely on thousands of applications to monetize the product for them," he said.

In a recent survey commissioned by the firm, 75 percent of IT executives in Indonesia said software testing plays a "very important" role in their businesses, while the rest said it was "important".

40 percent felt that budget-related issues were the main constraints to software testing, while 20 percent cited the inability to demonstrate return on investment (ROI).

Source: http://www.zdnetasia.com/growing-focus-on-independent-software-testing-62205000.htm

Did you like this? Share it:

Successful Software Testing Automation

 

Companies are turning to automated testing tools more often than ever before to ensure that their applications are working properly prior to deployment. That is particularly important today as more and more applications
are written for use on the Web which is the most public of arenas.

But for many IT and quality assurance managers, automation is a daunting task. So how do you get quick wins with automation? This article aims to help you develop a test strategy for automation that fits your circumstances:

1. Recognise that test automation is not automated software testing but computer-assisted testing.

Test automation may provide test execution elements, however what other ways could computers help testing. For example: test data generation; installations; file/database comparisons and analysing test results.

2. Decide what your automated test goal is (and re-evaluate your test mission as it may change)

Efficiency
This can be one Test Automation Goal, where the key aspects may be reducing testing costs, reducing the time in the testing phase, automating regression tests or improving test coverage.
Service
Tightening build schedules, preventing destabilization, playing to computer and human strengths and increasing management confidence in the product.
Extended testing reach
API based testing, component testing, model based tests, data driven tests and internal monitoring & control
Multiplying resources
Platform testing, configuration testing, model based tests and Data driven tests

3. Recognise that Test Automation scripting is akin to development and programming

When embarking on the use of scripted test tools the same practices used in software development apply. This includes code standards and reviews. The Key to success with scripting is to:

Generate re-usable components to maximize maintainability.

Use a data driven approach, so that a simple change to data can spawn a whole new raft of tests

Use keyword approaches to enable not technical users to ‘drive’ the automation.

4. Decide on the right tools

There are many automated testing tools that can aid testing from excel spreadsheets to Code analysers. The key here is to find tools that are right for your environment.

Commercial GUI Regression Test tools:
Mercury QTP, Winrunner, Compuware TestPartner, Rational Robot
Unit Test Tools:
nunit, junit, jwebunit, htmlunit Existing Development tools: Visual Studio Team test, perl, ruby
Open Source Test Tools:
Wink, rth, Fiddler, Selenium, WATIR, TestCaseManager, SwexplorerAutomation, ieunit, web test
What environment(s) do you wish to test?
Web, SAP, Client/Server, .net, Java, UNIX

It is all too easy, however to select an automation tool and be tempted to try to use it for the total automation of all applications. Some tasks do not lend themselves to the tool, but can still be automated using other tools such as command files or PC functionality. There may also be some processes where it is more efficient to test manually. You should not attempt to automate these.

5. Decide who will perform the automation and use the tools

It is critical to decide who is going to use/and or create the tools. Don’t treat test automation as a part time project. Allocate dedicated individuals time so they can provide real value. Overall when preparing a test automation strategy, plan to achieve small successes and grow.

Source: http://www.associatedcontent.com/article/112890/successful_

software_testing_automation.html?cat=15

Did you like this? Share it:

Software testing starts for the London Olympics 2012

 

The London Olympics organisation committee kicked off 200,000 hours of testing today in its 2,000m2 testing lab in Canary Wharf.

Led by London Olympics CIO Gerry Pennell, a team of up to 70 people will test all the software in the laboratory. The lab is split into over 50 individual cells that each focus on the software underpinning a different testing job. For instance, there are 35 cells testing the software for different Olympic sports.

When the lab has finished testing, the team will transfer all the software and the hardware to the Olympic venues for onsite testing.

The technology runs everything, from the timing of track events to the logistics of getting athletes around.

Gerry Pennell has experience of major sporting events and was previously director of technology for the 2002 Commonwealth Games in Manchester.

It is not possible to prepare for every eventuality in an event of the size of the Olympics. Former Olympic champion Sebastian Coe, who chairs the London Olympics planning committee, said the test team had to attempt to prepare for the worst. "We know things will happen that we cannot plan for, so we have to get our teams ready."

The security of data is a top priority. According to Atos Origin, when it ran the IT at the last Olympic games in Iberia, there were between 12 and 14 million data security events that needed to be checked-out every day.

The testing phase comes after two years’ work has been completed. The Olympic IT team completed the software designs in 2009 and produced the software in 2010. This year will see the testing phase with the operation phase next year.

Some of the software, such as the volunteer portal, are already up and running.

By the time of the Olympic Games in summer 2012, over 5,000 people would have been involved in the creation and implementation of the technology that underpins the sporting event.

The Olympics IT is being delivered by multiple suppliers. As a result, Pennell’s task is managing and integrating the contribution of multiple suppliers, with support from the Olympics main IT partner Atos Origin. He said he is used to managing multiple outsourced service providers, because that is the model that his previous employer, CFS, uses.

Atos Origin first became involved in Olympic IT in 1992 and by the 2004 Olympic games it was the main partner. It is already planning for the Olympics in Rio de Janeiro, Brazil, in 2016.

Because Atos has been working on the Olympics for nearly 20 years it has been able to innovate. For example next year’s games will see the Olympic data feed data in a standard format for the first time. Athletes, the media and officials will have a mobile application with bespoke content and a system that feeds information to commentators in real-time will be introduced.

Planning and implementing IT in any major project is challenging to say the least. Problems and delays can cost millions of pounds. The Olympic IT team cannot afford any delays and the reputation of an entire nation rests on its success in 2012. But Pennell, who was at the IT helm of Cooperative Financial Services (CFS) during the recent banking crisis, says: "Being a CIO at a bank during the credit crunch was good preparation for a project like this."

Source: http://www.computerweekly.com/Articles/2011/01/19/244968/Software-testing-starts-for-the-London-Olympics-2012.htm

Did you like this? Share it:

11 Ways to Improve Software Testing – Part 2

 

5] Give them business training. Station Casinos’ Andrew makes members of his testing department work the front desk, the casino floor and in different corporate departments so they can learn the lingo and better understand the systems they’re testing. (Most of his 125-person IT staff had never placed a bet on a sporting event at a casino prior to joining the company.)

6] Allow business users to test too. Most testing involves banging on systems and fiddling with code—technical stuff—which can tempt IT to leave business users out of the loop. Bad mistake. At La Quinta, "the testers are always coming out of the business community," says Novak, to ensure that the systems IT is developing meet their specs. For some applications, especially those that run in hospitals, getting end users to test applications is a matter of life and death. "Technology people can only go so far," says Patricia Skarulis, vice president of information systems and CIO of Memorial Sloan-Kettering Cancer Center. "We need to have users involved."

7] Involve network operations. Nate Hayward, vice president and director of quality management with HomeBanc Mortgage, says that during testing, his company’s network operations group uses a software tool (Compuware’s ServerVantage) to monitor servers for performance issues that could originate from the way hardware or software is configured. Involving the network operations experts in testing also gives them the opportunity to rehearse a deployment before a system goes into production, ensuring that the actual implementation will proceed smoothly.

8] Build a lab that replicates your business environment. Four years ago, Station Casinos built a costly test lab that looks like a minicasino with slot machines, point-of-sale terminals and Web-based kiosks that simulate the computing environments at all 13 of Station Casinos’ properties. Ninety percent of the applications the company runs, including wireless apps, are duplicated in the test lab. For the other 10 percent of applications, which are too big or complex to create an exact testing replica, Andrew comes up with a scaled-down subset of the app to predict how it will run when it’s fully rolled out. Or he gets help. With Station Casinos’ last system rollout, he used Microsoft’s test labs to run simulation models.

9] Develop tests during the requirements phase. Companies traditionally have waited to do testing until requirements have been established and coding has begun—or finished. A growing school of thought says that testing can still be done effectively even if the requirements have not been developed fully. Fans of "agile programming" (see "Fixing the Requirements Mess," Page 52) believe that testing should be done continually from the beginning of the project until the end.

10] Test the old with the new. EBay uses a statistical analysis tool it built in-house to compare defects discovered by testers to the code that was tested during a particular testing cycle. The goal is to make sure that previously tested pieces of software still work properly when new features are added. Pride says the statistical analysis tool pinpoints where testers need to add test cases in the current project and also helps determine the overall effectiveness of current regression tests for forthcoming software projects. EBay needs to continually refine the tests because some new projects may contain the same functionality as previous projects. The better those tests can be, the better future projects will be.

11] Apply equivalence class partitioning. This is a mathematical technique that testers can use to identify additional functional requirements that business analysts and users might have overlooked or not articulated, says Magdy Hanna, chairman and CEO of the International Institute for Software Testing. He says equivalence class partitioning gives testers a clear picture of the number of test cases they need to run to adequately exercise all of a system’s functional requirements. Pride says equivalence class partitioning is one way his group can determine all the ways in which eBay’s 157 million users might use its online auction platform.

Source: http://www.cio.com/article/14299/11_Ways_to_Improve_Software

Did you like this? Share it:

Trends in software testing for 2011

 

IT applications are increasingly constituted of complex business processes and are becoming more intricate and inter-connected. This aspect, combined with the pressure to reduce IT spend, is forcing enterprises to look for alternate ways to manage their growing portfolio of requirements; such as streamlining the quality processes, increasing the degree of test automation etc. In this context, I would like to briefly touch upon a few of the software testing trends for 2011 that I believe will make a significant impact on the testing scene.

What is a Trend?

I present an interesting definition of a “Trend” picked up from “Faith Popcorn’s BrainReserve”:

“Trends are not fads. Trends endure. Trends evolve. They represent underlying forces, first causes, basic human needs, attitudes, aspirations. They help us navigate the world, understand what’s happening and why, and prepare for what is yet to come.”

Key trends for 2011

Testing on the Cloud: To minimize test environment expenditures and gain better control of their IT resources, companies are beginning to take advantage of a delivery model known as ‘cloud computing’. In cloud computing, applications and information are provisioned on-demand, as a shared resource.

Cloud architecture can be set up as a “public” cloud – with services dynamically delivered from a third-party provider hosted outside of the firewall; “private” cloud – where a cloud-like architecture can be set up over the company’s private network (inside the firewall); or a hybrid model utilizing a combination of internal and external providers.

Traditionally, IT would have had to purchase additional server capacity and deploy it in their test environment, requiring added staff and extra maintenance expenses. Using the cloud architecture, IT managers are now able to quickly replicate their application test environment on the cloud and have the capacity they need “on-demand”. Companies are still cautious about moving all of their mission-critical applications to the cloud.

Agile Testing: Agile development methodology took the IT world by storm when it first emerged nearly 10 years ago. Organizations turned from waterfall and other traditional development methodologies to agile, hoping to improve business responsiveness, make their applications more adaptable to changing market conditions and enhance the quality of their IT systems. But these organizations are finding their own, unique forms of agile. Many organizations find success in taking the best of traditional methodologies and applying them to their agile projects, creating a unique hybrid model that works for them.

Agile Testing does not emphasize rigidly defined testing procedures, but rather focuses on testing iteratively against newly developed code. Quality is achieved from an end customer’s perspective. Agile brings the development and testing functions closer together, but it does not automatically turn developers into good testers, or make testers more familiar with the development process.

Organizations need to take a closer look at the skill sets required by the testing team to effectively support agile methods. Agile testers need to be more versatile than traditional testers. On the one hand, they must be more technical, more familiar with development practices, and comfortable with using non-traditional test automation tools to validate Graphical User Interface (GUI)-less applications. On the other hand, they need to be close to the business to understand the requirements, work with end-users throughout the project, react quickly to change and tie application quality directly to business value.

Right Information at the Right Time: As James Whittaker, an international speaker once pointed out: “Information is at the core of everything we do as software testers. The better our information about what the software is supposed to be doing and how it is doing it, the better our testing can actually be. I find it unacceptable that testers get so little information and none of it is specifically designed to make it easier to do our jobs. I am happy to say that this is changing… rapidly…. and that in the near term, we will certainly be gifted with the right information at the right time.” This is definitely one of the trends that will change perceptions in 2011.

Skilled Testing resources: Organizations are constantly on the lookout for better skill-sets and test profiles that can add real value to improving the quality of software. In the past, the development team would typically test the systems they developed. Today, the profile of a tester is changing rapidly and organizations prefer testers who bring both strong technical skills and the relevant domain and business knowledge to the table. In addition to being knowledgeable about automation technologies, testers today are able to understand the purpose of business solutions & requirements and contribute intelligently to improving the quality of the system. They are also able to provide actionable analysis to the development community, for faster resolution of defects. Testing is increasingly seen as being closer to the business and considered a very progressive career path with multiple roles and responsibilities.

Analytics / BI (Business intelligence) Testing: In today’s fast paced business environment, it is almost always an unstated fact that the success of any BI (Business intelligence)/ Data Warehouse solution lies in its ability to not only analyze vast quantities of data over time but also to provide stakeholders and end-users meaningful options that are based on real-time data. This requirement mandates an extremely efficient system that can extract, transform, cleanse and load data from the source systems on a 24/7 basis without impacting the performance, scalability or causing system downtime.

One of the key elements contributing to the success of a BI (Business intelligence)/Data Warehouse solution is the ability of the test team to plan, design and execute a set of effective tests that will help identify multiple issues related to data inconsistency, data quality, data security, failures in the extract, transform and load (ETL) process, performance related issues, accuracy of business flows and fitness for use from an end user perspective.

The primary focus of testing is usually on the ETL processes. This includes, validating the loading of all required rows, correct execution of all transformations and successful completion of the cleansing operation. The team also typically thoroughly tests SQL queries, stored procedures or queries that produce aggregate or summary tables. Keeping in tune with emerging trends, it is also important for the test team to design and execute a set of tests that are customer experience -centric.

Reusability of testing assets: Organizations are investing time in quality solutions where they reuse 45-60% of their testing assets, leading to increased testing efficiency, high level of test case automation and shorter testing cycles.

Test automation solutions: Organizations are investing on resources to implement test automation solutions to increase time to market, save money, improve accuracy, increase test/requirement coverage and improved team morale.

Summary:

Many of the trends outlined in this paper are fast being seen as business-as-usual practices today. However, these trends are still evolving and lean towards bringing in measurable gains to the business community, so the budgets for IT testing are justified.

Source: http://www.ciol.com/Developer/Testing/Feature/Trends-in-software-testing-for-2011/145154/0/

Did you like this? Share it:

QA InfoTech Announces Top Trends in Software Quality for 2011

 

QA InfoTech, a 400-person independent quality assurance and software testing firm with five testing Centers of Excellence in the United States and India, today unveiled the top trends in software quality for 2011. Software quality is expected and demanded by consumers now more than ever. In 2010, it became rare for any software company to skip quality assurance altogether. This upcoming year, quality will be integrated at earlier stages in the product development lifecycle, and metrics and test automation will play greater roles.

“Software companies have had to dramatically change their approach to quality to create the more usable and higher quality products that consumers are now demanding,” said Mukesh Sharma, CEO of QA InfoTech Worldwide. “As a result, customers are more satisfied and satisfied customers mean greater revenue for software companies— everyone wins.”

Some of the top trends in software quality are:

1. Quality is no longer an afterthought in product development, but rather a core part of the process from the outset. Quality assurance engineers are increasingly helping to plan for quality and create timelines of relevant metrics at the outset of product development rather than being the “defect finders” later in the process. By providing insight and planning for quality in the early stages, including how to avoid common quality mistakes and how to make products more testable, quality assurance engineers deliver significant positive impacts on products. With the early integration of software quality engineers, products will increasingly be delivered on-time and at the quality-level consumers demand.

2. Independent quality assurance testing is a form of risk mitigation for projects. Companies understand that software development creates a business risk, whether the end-product is for third parties or for use internally. By looking at quality throughout the product development process and meeting important test metrics set up by independent quality assurance teams, companies mitigate their business risks of product failure, customer dissatisfaction and project cancellation. Software quality assurance has become another form of business insurance.

3. There will be less reliance on formal tools and instead a greater use of frameworks built using open source. Increasingly, quality testing frameworks are being developed using open source tools such as Selenium and JMeter. Formal tools from companies such as IBM and Hewlett Packard are still being used, but are being augmented, and sometimes replaced, by test automation frameworks created using open source. This brings down testing costs for companies, sometimes by hundreds of thousands of dollars, and often these savings are passed on to consumers.

4. Companies are setting up test labs in the cloud rather than building them in-house. By using the cloud, companies can test high loads and eliminate costs associated with owning and maintaining hardware. Virtualized images of configurations are increasingly being used to increase efficiency and reduce set-up costs. The result is an ability to test more platform combinations, faster reporting and fewer test machines that ultimately end up in landfills.

“In 2011, there will be a focus on software quality like never before,” continued Sharma. “Consumers are demanding it more than ever and software companies are discovering the positive impact quality has on their bottom-line. It is very exciting time in software quality!”

QA InfoTech Independent Quality Assurance Services

By providing end-to-end software testing, and using its proprietary testing frameworks developed using open source technology, QA InfoTech (an ISO 9001:2008 certified company) reduces costs and time-to-market for its clients’ products in addition to improving overall product quality. The company offers everything from functional testing to globalization and internalization testing, automation frameworks using open source technologies, performance testing, security testing, usability testing, mobile testing and much more. QA InfoTech specializes, and has domain expertise, in several industries including education, publishing, banking and finance, mobile, retail, cross-industry, government and healthcare.

Offering comprehensive and world-class testing facilities that can scale at short notice using virtualization and cloud computing technologies, and that include state-of-the-art hardware, server infrastructure, mobility labs and high-bandwidth Internet-connectivity, QA InfoTech can take on software testing projects of just about any size. QA Info Tech has been actively serving the North American market for more than six years and counts companies such as Adobe, Harvard Business Publishing, The Princeton Review, Scholastic, Ooyala and ideeli as clients.

Source: http://www.prweb.com/releases/2011/01/prweb4959164.htm

Did you like this? Share it:

11 Ways to Improve Software Testing – Part 1

 

Three years ago, Station Casinos came up with a great promotion to lure customers: $25 worth of free slot play on their electronic loyalty cards. It worked like a charm too. Gamblers flocked to the casino in droves.

That should have been a good thing.

But one Friday night, shortly after the promotion began, when players inserted their cards into the slot machines, nothing happened. The sheer number of people trying to access the machines—at the same time the accounting department was running a number of financial applications—caused the servers that stored all the promotional information to freeze. Irate, players threw their loyalty cards on the floor and raised a ruckus. That was a bad thing.

The source of the problem? Testing. Marshall Andrew, Station Casinos’ VP of information technology and CIO, says Station Casinos never anticipated such an overwhelming response to the promotion. Consequently, IT did not test the system for such large volumes of activity, and certainly not while other programs were running. Station lost the cash they would have made that Friday, alienated customers and had to run another campaign to apologize; the casino invited some customers to return another weekend for $50 worth of free slots.

The moral: Testing is essential to developing high-quality software and to ensuring smooth business operations. It can’t be given short shrift; the consequences are too dire. Businesses—and, in some cases, lives—are at risk when a company fails to adequately and effectively test software for bugs and performance issues, or to determine whether the software meets business requirements or end users’ needs. (See "The High Cost of Flawed Testing" on Page 66.)

"The important thing when you roll out a system is to make sure it works," says Andrew, who has made significant changes to his testing organization (known as quality assurance, or QA) since then. First, he changed the testing process itself. Previously, developers had a great deal of freedom to change code while it was being tested to keep the project moving. Now, there are tight controls on the developers’ access to test code. To keep everyone honest, Andrew had the QA specialists begin reporting to the business analyst group rather than to the development group, whose work it was evaluating. Next, he hired more QA specialists—with business training—and involved them in the development process earlier, when business analysts are creating requirements documents, so that they can then develop test scripts based on business specifications right from the beginning.

The following list of best practices for testing software and running your testing organization were gleaned from interviews with companies that have rigorous testing needs and standards. These tips go beyond the "test early and often" mantra and will improve your IT organization’s testing capabilities—not to mention the quality of the software you release.

1] Respect your testers. In many companies, testing is an entry-level job. As a result, testing isn’t done well. Instead of hiring people off the turnip truck, recruit candidates who are detail-oriented, methodical and patient. Look for people who know how to code. Your developers will respect them more, and they can code some of their own testing tools. "If the development organization and the QA organization don’t respect each other, we won’t be able to achieve our high-level quality goals," says eBay’s VP in charge of QA, David Pride.

2] Colocate your testers and developers. Putting developers and testers together goes a long way toward improving communication between two groups that often lock horns (after all, testers are paid to find fault with developers’ work). Physical proximity "facilitates the nuances of testing" that are best communicated through personal interaction rather than by e-mail or an application development workflow tool, says Pride.

3] Set up an independent reporting structure. Testing should not report to any group that’s evaluated on meeting deadlines or keeping costs down for a project, according to John Novak, senior VP of hotel chain La Quinta. Having testers report to the development group is the worst choice of all, Novak says. If developers are behind or having trouble with code, they will be tempted to keep testers out of the loop. Instead, Novak has testers report directly to him. Andrew has testing report into his business analyst group as a way to foster communication and to get testers involved in the development lifecycle early.

4] Dedicate testers to specific systems. At Barnes & Noble, one group of testers focuses on store systems, while others tackle financial and warehouse systems. Barnes & Noble CIO Chris Troia says focusing testers on one set of systems deepens their understanding of how those systems are supposed to work and gives them the expertise to identify problems that might not show up in a formal test document. EBay takes the same approach, but goes one step further. The company has three distinct testing groups: one for site functionality, one for payments and one for data warehousing applications.

Source: http://www.cio.com/article/14299/11_Ways_to_Improve_Software

_Testing_

Did you like this? Share it: