Testing Practice Quality
We test a product/solution/snippet/module/component under a definite plan, taking full preparation to the extent possible and feasible for random, accidental and undocumented features.

Our Inputs To Testing Process
The input is expected to come from the development team after the unit test is completed. The development team provides the basic requirement document(s), any client supplied artifact to help the development process, any limitation document and the contract document sans the commercial portion.

Types of Testing
The types of testing undertaken are:
  • Smoke Test
  • Design module test
  • System Test
  • Integration test
    • Black box test
    • White box test
    • Code level test
  • Acceptance test
  • Product Release/Solution Release test
    • Veracity test
    • Boundary test
    • Feasible and plausible value test
    • Usability test
    • Concurrence test
    • Cross Application test
    • Regression test
      • Load test
      • Performance test
      • Pattern test
      • Distribution test [where data in input in different statistical distribution pattern]
      • Simulation test
  • Configuration management
  • Release notes template preparation
Test Plan Preparation
The types of testing undertaken are:
  • Test cases are planned through user cases.
  • Test use cases are compared with Use cases of SRS.
  • Test cases generated or prepared
  • Test results are connected to each test case
  • Test traceability matrix generated with Test case, Use cases, test values, expected values and results
  • Test plan registered through Configuration management
  • Test plan published.
Test Results Registering
Usually open source tools are used like Bugzilla, and other newer open source utilities.


Test Level Reporting
The levels of bugs are usually reported through a two dimensional Severity/Priority matrix with the following Severity levels
  • Show stoppers
  • No workaround
  • With Workaround
  • With Multiple workarounds
  • Medium level bugs
  • Cosmetics
  • Nice to have removed or modified.
Technology Stack
The levels of bugs are usually reported through a two dimensional Severity/Priority matrix with the following Severity levels
  • Unit/Regression Testing
    • JUnit, JRun, JTest, NUnit, TestDriven .NET
    • Rational Test Studio & Rational Test Suite
    • WinRunner
  • Load/Performance/Memory Leakage testing
    • LoadRunner
    • WebLoad
    • Rational Performance Tester
    • TestDirector
    • WinHex
    • FxCop