| |
A Software Product Testing Project
Project Fact
| Client Industry |
Independent Software Vendor |
Services provided |
Software Testing |
Outsourcing Model |
Offshore Delivery Center (ODC) |
Product Types |
Client Application + Server Application |
Testing Environment |
• Windows Vista/2003/XP/2000
• MS Office 2007/2003/XP/2000
• MS Exchange Server 2003
• MS SQL Server 2005/2000
• Lotus Domino 6.5
• Lotus Notes 7.0/ 6.5.x / 6.0.x |
Environment Languages |
English/French/German/Chinese Simplified/Chinese
Traditional/Japanese/Korean |
Testing types |
• Manual Testing + Automated Testing
• Unit Testing
• System Testing
• Black-box Testing |
Project Duration |
30 months |
Peak Resource |
13 |
Challenge
The customer is a London-based leading software provider focusing on secure content compliance solutions. The customer's primary products ensure document accuracy, security and compliance. Based on our long-term relationship, the outsourcing project is to test stability of the customer's software build over build in different environments.
Solutions
1.Sanity/Smoke Testing
Once a new software build was available to test, a Sanity/Smoke test on the new build would be executed at the first stage. The purpose of the Test was to verify whether there was any noticeable or regression defects of GUI, buttons and major functions of the software.
2.Globalization / Localization Testing
The stability test on the software Unicode builds should be executed in comparison to ASCII builds, in order to find any noticeable regression between them.
The approach is that each tester works on two computers with the same testing environment. The only difference is that one computer is installed with the Unicode build and the other with the ASCII build. Testers should carry out the same test on both of the Unicode and ASCII environments to find any noticeable difference between them.
3.System Testing
We executed test case based test and exploratory test repeatedly during the whole project lifetime. There were at least two phases: Phase I: All major functions and operations of the software were covered.
Phase II: Advanced test based on Phase I. More function details and various using possibilities were considered in this phase.
4.eXtreme Test
MDT adopted eXtreme testing methodology in this project, and execute test in parallel with customer's development team: MDT reports bugs found out on a current build to the customer; The development team from the customer's side fixed these bugs and then released a new build to MDT; MDT verified the changes and keep on testing on the new build. That is to say, the customer constantly released new builds to MDT as some current bugs were fixed. And MDT verified these fixes and continuously tested on new-released builds.
Benefits
• Guaranteed product stability against a large amount of environments
• Real-time update to test case and test data
• Real-time bug fixing verification in parallel with their global development teams
• Iterative test following the customer's eXtreme programming methodology
• Scoping bugs in an early stage
• Providing bug reports on a daily basis
• Stability test in English, Chinese Traditional, Chinese Simplified, Japanese,
Korean environments
|
|
