This is a challenging job where in we check all the possibilities to test a particular feature. We put our heart and soul in finding a bug to make sure this bug is not encountered by the end users.
Testing Types like Unit, System, Sanity, Functional, Stress, Performance, Interoperability, Negative, Regression Testing and many more based on requirement are undertaken and executed appropriately.
Development of a standard test plan is a part of our routine. Following which we create suitable test cases and execute them to find if the application is perfect.
Validation of a program/application/product is done by testing it by keeping ourselves in the shoes of the end users. We put in our best efforts to cover all possible variations for testing the application.
Learning from the previously implemented methodologies in testing helps us in achieving our targets under strict deadlines and heavy pressure. Working as a team makes us more confident in validating a product. Testing plays an important role in development of new IT programs.
We test software for the purpose of locating and eliminating bugs in the product and involved from Requirement phase to release phase.
Various phases we involved in testing are:
- Sanity testing/Unit testing
- Functional testing
- Interoperability testing
- Integration testing
- Negative testing
- Security testing
- Regression testing
- Performance/stress testing
We have involved in Testing automation testing tool itself and network products like switches and access-points. Created more than 100 test plans and 1000’s of test cases to verify the upcoming features and conflicts between testing team and development team.
We involved in Reporting test results and enter problems and issues into the bug database called Jira and Bugzilla. Monitor and update bug reports as mentioned by bug report closure.
We are also involved in testing Traffic generation applications like Ixia, Spirent and Agilent.
Testing artifacts used for testing process:
- Test plan
- Test case
- Test suite
- Test harness
We create test artifacts based on the following scenarios:
- Positive scenarios
- Negative scenarios
- Boundary conditions and
- Real time scenarios
Building a quality product requires testing throughout the product's life cycle, from requirements review to test case review, functional testing to compliance testing, and from test strategy to test automation. Paxterra offers a tailored software-testing package as part of the development cycle Tact and diplomacy are useful in maintaining a cooperative relationship with developers, and an ability to communicate with both technical (developers) and non-technical (customers, management) people is useful.
Our QA and testing professionals offer the following services:
- Module testing
- System testing
- Integration testing
- Load and stress testing
- Performance testing
Generating a ‘good’ set of test cases, the test designers must be certain that their suite covers all the functionality of the system and also has to be sure that the suite fully exercises the GUI itself. Test plan document formats can be as varied as the products and organizations to which they apply. Testing that seeks to regression in existing functionality after changes have been made to the software, such as functional enhancements, patches or configuration changes.