Test Management Process

Test Strategy Design

A test strategy is an outline that describes the testing approach of a software development life cycle.
It is created to inform project managers, testers, and developers about key issues of the testing process. This includes the testing objective, methods of testing new features, total time and resources required for the project.

At HSC, we recognize this and publish a well-defined test strategy which highlights product risks of the stakeholders, mitigation approach, types of tests to be performed with entry and exit criteria.
It also outlines items like test phases, roles and responsibilities, tools to be used, test schedule/effort, automation strategy, risks and test reporting.

Some Case Studies

• Developing test strategy for tier-1 routers and switches networking OEM’s enterprise SDK development project
• Developing test strategy of OSS/BSS project involving their web application and web services testing
• Developing test strategy for Packet Control Function node in CDMA/E-VDO network

Test Setup Design

A typical test bed/test environment includes specified hardware and software which can be used to perform testing for the system under test. For test setup HSC follows a robust process involving setup of environment for testing (setup of required hardware, software and networking requirements), deployment of releases, sanity on the test bed environment, the test bed environment approval by all the stakeholders and required test data configuration for the system under test.

Some Case Studies

• Test setup for OSS/BSS projects, to perform functional and performance testing of web applications and web services testing
• Remote lab test setup for functional and performance testing of embedded media player across multiple devices

Test Planning

A test plan documents the strategy that will be used to verify and ensure that a product or system meets its design specifications and other requirements.
A test plan identifies requirements, risks, test cases, test environments, test schedules, and other related items.

Success of any testing is determined by test planning as this ensures good quality. At HSC, we recognize this and we involve the test team right at the time
of requirements discussion and follow processes outlined below to ensure proper test coverage.

• Requirement Specification: Conduct a walkthrough of the business requirements and design documents to understand more about the system to test
• Develop test requirements: Confirm that all the requirements of testing are addressed.
• Define test types: Define types of testing that will be conducted prior to release, e.g. SI and SSI testing, Release testing, Regression testing, Acceptance testing
• Define test deliverables: Define the test artifacts that will be delivered at the end of a phase
• Define techniques used: Decide the testing methods, by which each type of testing will be conducted, e.g. manual testing, automated testing with the respective tools that may be used
• Identify constraints and risks: Perform a risk assessment on the test requirements
• Reporting documents:Provide a list of all reports that will be produced in test life cycle
• Defect management: Classify defect categories per their severity and priority

Some Case Studies

• Test Planning for Perl based automation framework to drive Single UE and Multiple UE test scenarios for doing load and performance, functional testing
• Test planning for GSM Field Simulator (GFS), integrated with their embedded GSM modems, providing functional and load testing of GSM BTS Indian OEM
• Test planning for cloud based deployment of CRM and BSS web application on SalesForce

Test Procedures

A test procedure defines the aspects that must be validated to ensure that the system is working as desired and is built with a high level of quality. This can be a single step, or a sequence of steps to test the correct behavior/functionality and features of an application.

HSC test procedures adhere to the following steps to ensure the test procedures are written in the best way.

• Write test cases:Prepare test cases from the requirements document and/or using any inputs on requirements during the development phase like use cases, screen mockups, wireframes or prototypes
• Preconditions: Define preconditions to test cases that must be met before the tester can run the test case or test suite
• Templates:Define the template for the test cases. Any test case should contain information like, test category, test case ID, test case description, requirement ID, author, status, manual/automated etc.
• Test Tools Selection: Evaluate test tools against criteria for tool selection and document the evaluation report
• Traceability matrix: Maintain traceability matrix by tracing each test case in the test case document to the corresponding features in the requirements and design document

Some Case Studies:

• Test procedure for Perl based automation framework to drive Single UE and Multiple UE test scenarios for doing load and performance, functional testing
• Test procedures for integration testing of DSL field testing handheld equipment to run end to end functional tests on these devices
• Test procedures for field test mobile application for Android, used for measuring network performance and run wireless network tests