LogicTree QA and Testing Focus
As LogicTree has partnered with several product development companies and IS/IT organizations, it’s focus on testing starts with inception phase. We believe that test cases will reflect the features of the system and hence should be written as part of the inception phase. It is our firm belief that development and unit testing go hand in hand and the developer should be responsible for writing the unit test cases where possible. For integration testing, manual testing or using test harnesses and other tools would be recommended. For System Testing, Performance Testing and Load Testing the process relies on a variety of proprietary and open source tools.
Tools
- Segue suite
- Mercury suite
- Rational suite
- Web Services Testing Tools
- Defect Tracking Tools
LogicTree’ ‘scenario-driven’ testing Methodology
LogicTree uses a ‘scenario-driven’ testing Methodology. According to the type of testing being performed, business functions or processes will be selected and realistic business scenarios and test data will be developed to test. The expected results of the tests will be determined in advance of the tests and documented for comparison with actual results. The outcome of the testing will be recorded in detail in the individual scenario documents and summarized in a status log maintained for control purposes.
The basis for the tests will be the ‘to-be’ business processes as defined in the project/product scope to establish a process-oriented way of testing. Based on the business processes multiple test scenarios will be defined to simulate the various business conditions. The test scenarios will be set up in such a way with clear reference to the scope, process steps and any other variants.
The Integration Test will go through a number of Cycles. The definition of a cycle can vary by project and deployment phase. However, the typical cycles for a Template development and deployment are based upon functional tests in five cycles. User requirements drive design that drives various functional tests. Complexity of integration will increase as deployment rollouts continue. Our cycles can be defined as:
- Cycle 1 - all security (jobs) will be tested positive and negative
- Cycle 2 - all in scope functionalities will be tested as part of integrated scenarios (including enhancements, integration, reports and security). The scenarios will increase in complexity and integration aspects.
- Cycle 3 – defined regression tests will be executed again after special events (e.g. application of support packages) to retest functionality that has already been confirmed in a previous test.
- Request Enterprise Testing services quote or you may please feel free to directly Contact us |
