Offerings

Test Framework Design: Once the test strategy is decided, QA team at PSI decides upon the test framework design, which has to be robust and meeting the required test guidelines.

• The purpose of the test framework is kept to provide a reasonably simple but powerful framework for testing the application or the product
• Test Frameworks if required are designed to be platform independent for cross platform applications
• Test Framework is designed based on the test documents, test cases, level of testing required, load support to be certified for the product/application
• Team decided upon the design of the test framework based on a number of artifacts like the test product follows the Object oriented structure or requires just the web page testing
• At PSI the team holds the experience in designing frameworks for Object Oriented as well as web interfaces
• To highlight a few test frameworks have been designed over JUnit, Jperf, JMeter, custom frameworks using java classes or XML frameworks

Authentication/Regression Testing: PSI has performed functional and regression testing for a number of products. Our engagement teams have the experience to identify the test cases and design the test suite for vigilance of any regressions introduced in the test system. To give the clean chit against any regressions the highlights covered by the team are:

• Whether to replicate all or a relevant part of the product/application testing in local QA laboratory or to connect directly into the client’s environment, which includes the geographically remote sites also
• Creating the complex test suites and Selecting the right tool to use. We have experience in using all the leading test tools including, WinRunner, QTP, TPTP
• The communication model to be adopted for reporting progress on the testing process. The team also participates in triage to help expediently resolve identified issues
• Selecting the appropriate defect tracking system to report issues
• We have experience in Bugzilla as well as Test Director

Performance Testing: The objective of this test case specification is to test the Performance on supported test configurations. The goal is to ascertain the event performance in terms of throughput and latency. Along with that the system reliability and stability are one of the key objectives. Testing frame work will focus on test runs over current release builds:

• The performance testing is covered to measure the performance in distributed environment, and the impact on performance with varying number of users, varying objects and metrics of load
• As per the robustness required the performance tests are on a regular builds to measure any degradation
• The performance test results are archived for every major, minor and patch releases
• Scalability tests and capacity planning are also done in conjunction with performance tests
• Performance test team designs the framework to determine the throughput and latency statistics
• Ensure the Reliability and Stability in case of recoveries after system break down or crash situations
• In case of server-client applications, team assures for server side Analysis including the memory consumption in processing the requests, figuring out the cause leading to actual bottlenecks
• Monitoring the performance degradation from single user to multi user work load
• Team at PSI also hold expertise to take care of the performance effects including different implementation modes for database based applications

Certification (Product Readiness) : Systematic and planned methodology is followed strictly at PSI to ascertain the product readiness and certify the quality of the product:

• The general practice followed is to perform a number of test cycles overlapping with the development phase for the QA release builds
• Once the product is feature complete the code is freeze and thereafter the GA quality is achieved
• Once the feature quality attains the acceptable level the product readiness is assured based a number of factors

Product Development Assurance Cycle:

• Unit Testing
• Beta Quality
• FCS Quality is determined varying the following parameters
• How many cycles
• When changes stop
• Regression testing
• Who decides a release is ready?
• QA’s role
• Support’s role
• Technical Pubs
• Product Management Signoff
• Using Postmortems to improve quality

Feature Readiness (QA quality):

• Feature Complete
• Unit Tested by Development Team
• Ready for QA Testing (no known P1/P2 issues)
• QA engineers pick up the weekly builds with the feature and start covering tests
• Test coverage is reported on a daily basis and tracked via test case specification

Feature Readiness (GA quality):

• Independently Tested by QA based on a Test Case Specification
• All bugs entered and triaged in Bug Logging tool like Bugzilla
• All known P1 issues fixed
• All known P2-P3 issues are fixed, deferred or worked around

Product Readiness: Product Readiness is finally determined upon a number of test accomplishments.

• Migration/Upgrade Tests
• Import/Export Tests
• Multi-User Tests
• Stress Tests
• Performance Tests
• Usability Tests
• Error/Exception Tests
• Installation Tests
• Longevity Tests – 72 hours of continuous operation
• Restart/Recovery Tests
• Persistence tests
• Platform Matrix
• Documentation Review
• Bug Verification