Testing Procedure

Testing Procedure for the Software Products

What is 'Software Quality Assurance' ?
Software QA involves the entire software development PROCESS - monitoring and
improving the process, making sure that any agreed-upon standards and procedures are
followed, and ensuring that problems are found and dealt with. It is oriented to 'prevention'.
What is 'Software Testing'?
Testing involves operation of a system or application under controlled conditions and
evaluating the results. The controlled conditions should include both normal and abnormal
conditions. Testing should intentionally attempt to make things go wrong to determine if
things happen when they shouldn't or things don't happen when they should. It is oriented
to 'detection'.
Organizations vary considerably in how they assign responsibility for QA and testing.
Sometimes they're the combined responsibility of one group or individual. Also common
are project teams that include a mix of testers and developers who work closely together,
with overall QA processes monitored by project managers. It will depend on what best fits
an organization's size and business structure.
Testing methods and procedure for the product.
The company will start testing of each product after design stage is completed. By that time
the software requirement study (SRS) is finalized and get signed by the customer. The SRS
document will be studied and reviewed by the testing department. After freezing the SRS,
Prototype of the product is developed by the development team. Also low-level design
document, high-level design document, Flow chart & ER diagram of the product are
developed for the product. Prototype reassembles the dummy product without the code.

Testing & Validating the Prototype & Documents

After the prototype is developed, it is checked & validated by both
development team & testing team. The prototype is checked and tested whether it is
designed according to the customer/client requirement. All documents prepared for the
product are studied and reviewed by the test lead & test engineers.
The prototype developed will get approved from the customer/client, & if any changes are
asked or informed by the customer/client then it will be done in the prototype. Finally the
client must approve the prototype. The testing team tests the final prototype & all the
changes made are traceable to the testing team. All documents LLD, HLD, Flowchart & ER
Diagram are reviewed & studied by the testing team members & they are sure that
understood the functionality & workflow of the product.

Testing Procedure

Preparation of Test Plan & Test Cases of the product.

After prototype is finalized, development team will start coding. The testing
department lead will prepare test plan. The test plan is developed for the product. The test
plan will contains the details of the test engineers to test the product, Features to be tested,
Test strategy details, Test Responsibly matrix, Test schedule activities, Defect
tracking/Reporting, Issues/Risks & Contingencies of the product. Finally the Test plan is
reviewed & approved from the Project manager, Development team lead, and Test team
lead.
The number of test engineers required for a product is depends on the type of the product,
its size & resources available for that product. Decision for the selection of members will
be left to the test lead or senior technical leader. After selection of the test team members,
the test engineers will start to write the test cases for the product.
Unit Testing
Unit testing for the products are done by the development team members. The
developers will do the unit testing & if errors are found then they rectify & correct the
errors.
Integration Testing
Integration testing for the products are done by the development team members.
The developers will do the integration testing along with the test team members. Both test
& development team members will do the integration testing. Any changes on integration
& architectural design of the product will be reviewed & discussed by the both teams.
Finally the integration testing is completed & should get sign off from the both the
development & test team members. The selection of test engineers & the development team
members for integration testing will be decided by the both development & test team
leaders.
Writing Test Cases for System Testing
The purpose of System Testing is to establish confidence that the
Application Under Test (AUT) will be accepted by the users (and/or operators), and to
avoid errors in the live system that will have an adverse impact on the business from a
functional, financial or image perspective. Test cases for the product are written on basis of
the system testing. For our company products & for on site products test cases are written
for system testing. System test case for the product is written with the help of Prototype,
Flow chart, ER Diagram, HLD, LLD, SRS, & Use Case documents. Test cases are written
as that it covers the overall working & functionality of the product. All the functionality
test of the interface will be done in system testing. Finally the tests cases are get approved
by the Test team lead & Development team lead.

Testing Procedure

Test Schedule
Test schedule will track the details of the test documentation, test development, test
execution activities. Test schedule activities are measured & tracked down in terms of
person-days & the actual completion of the particular activity. These activities details are
maintained & measured in the test plan.
a). Test Documentation
Test documentation in the test schedule will keep track of the test plan, test
specification, test validation report & test summary report details. It maintains the details of
all activities with development time, signoff date, & dependencies. Each document in the
test documentation will be monitored with development time, signoff date, &
dependencies.
b). Test Development
Test development will holds the deliverables of the testing. It maintains the
details of all the deliverable documents with development time, signoff date, &
dependencies. Test automation suite, Functional test suite are deliverables that are
maintained in the test development. Each deliverable is maintained with development time
& dependencies.
c). Test Execution.
Test execution will maintain the details of the Unit testing, Integration testing,
system testing, User acceptance testing, functional testing, regression testing,
documentation review, total test cycle along with their Execution time &dependencies. The
execution time for each activity will be measured in terms of Person-Days. The execution
time will shows the details of the time taken to do & execute the each activity.
The dependencies details will show the person names responsible to do testing for the each
test activity. Another table, person responsible for testing, will hold the dependent person
name, application part/modules to test, along with their date. All the details of the each test
activites are entered and maintained in the test execution table.
To start system testing, product must get through & complete the stages of both unit &
integration testing conforming that there is no error/fault from the unit & integration level.
System testing is done on the basis of the test cases developed. Test data required to do
testing are generated manually. System testing is said to be complete when all the test cases
executed atleast once. System testing of a product can be done more than one cycle.
Functionality testing, Stress & Load testing are also done along with the system testing.
After execution of all system test cases, test validation report is prepared.
Test Validation Report.
Test validation report is prepared to shows the details of the test cases that
are failed, Not Executed. System test case sheet holds the information of the test case that
are passed, failed, Not executed test cases details along with their Priority & severity,
expected & actual result of the failed test cases. From the system test case sheet, failed &
not executed test cases are entered in the validation report. Test validation report contains

Testing Procedure

the test cases ID & test case description that are failed & not executed, actual result arrived
on executing the test cases along with their severity, phase introduced, defect category of
the test cases. Finally the test validation report provide the complete information of the test
cases that are failed & not executed with their complete details. Severity & Priority ratings
of the defect/bug for the failed & not executed test cases are given as following.
Priority
P1 Low
P2 Medium
P3 High
P4 Very High

Severity
P1 - Low
P2 - Medium
P3 High
P4 Very High

Test Summary report

Test Summary report will hold the details of the number of test cases in the
particular procedure/module, No of test cases passed, Identified bugs/defects category (P1,
P2, P3, P4) priority, remarks, prepared by, released status, authorized by details. According
to procedures & no of test cases, summary report calculates the number of test cases passed
at cycles (I, II, III) percentage. A bar graph shows the No of bugs in each defects
category (P1, P2, P3, P4) of all the procedures in that particular cycle. Both test validation
& summary report development time, dependencies & sign off dates details are entered and
maintained in the test documentation.
Defect Tracking & Reporting
Finally the Track defect report document is prepared to log the bugs/defect that
are traced during system testing. It prepared from the test validation report which has the
complete details of the failed & not executed test cases. This report is prepared for the
developers to fix the defects so that they can clearly understand what the defect is & where
it had happened & lies. The defect report has details of the Procedure/SI No, Test Set,
Screen, Defect category/Type of Error & Description of the Defect. This defect report is
reviewed & approved by Test Team Lead, Development Team Lead, & the Project
Manager. Track Defect Report is named as per the cycles the product had taken for testing.
Persons Responsible for Bug fixing & Regression Testing.
After the approval of the defect report, it will be handle to the development team
lead. Development team lead will assign the works to the developers to fix the bugs & the
developers responsible for fixing the bugs are entered in the persons responsible for bug
fixing table. After bug fixing, regression testing is done for that procedure. Test engineers
responsible for regression testing will be assigned & decided by the test team lead. Test
engineer names, procedure/application to do regression testing along with their date are
entered and maintained in the Persons responsible for regression testing table.
In regression testing, if the bug found is not fixed, it will be assigned back to the
developer who had already involved in that bug fixing. After cycle I regression test, if any
new bugs/defects are found, it will be assigned as test cycle II, then test validation report,
summary report, defect report are prepared for that cycle, & also bug fixing by developers,
regression testing by testers are done for that cycle. Like this, test cycle process continous

Testing Procedure

till all the system test cases are executed correctly with pass status. System & Regression
testing execution time in person-days & dependencies are entered & maintained in the test
execution table.
Load, Volume and Stress Testing
Load testing is done for the product to determine how well the software
behaves in high load conditions, what its response time for the particular actions. The
volume testing for the product is done to check & validate that developed software will
handle large amount of data. The purpose of Volume Testing is to find weaknesses in the
system with respect to its handling of large amounts of data during short time periods.
Stress Testing is done to ensure that the system has the capacity to handle large numbers of
processing transactions during peak periods. Both the volume and stress testing are done
after the system testing is completed successfully.
Performance Testing
Performance Testing is accomplished in parallel with Volume and Stress
testing, to measure system performance under all load conditions. System performance is
generally assessed in terms of response times and throughput rates under differing
processing and configuration conditions. Performance testing is done to cover performance
under all hardware and software system configurations. Performance testing for the
product is done to determine that the system meets specified performance objectives, to
tune the system, to determine the factors in hardware or software that limit the system's
performance, and project the system's future load- handling capacity in order to schedule its
replacements. Performance testing of the product will determine the overall performance of
the product that has developed & to check, validate how well it perform on various
working condition.
User Acceptance Testing
User acceptance testing is done for all products that we do testing. This
testing is done for user/customer purposes to check & validate that the software is
developed according to the user needs & requirements. It is the final testing based on
specifications of the end-user or customer, or based on use by end-users/customers over
some limited period of time before the product is implemented in the customer
environment. Also the product is tested for user friendliness. Any changes suggested by the
customer will be immediately get focused & discussed by the project leader.