Travel Tech

The Problem

In this case, the problem was that client was not sure from where to start, how to start, what was expected out of testing, what all kind of testing he needed. The only thing which was known to him was
that he had a very complex system from Travel domain with five different parts and almost all were on
different platform. It was combination of three web applications, two Android Apps and Android apps
were having iOS versions as well. As the development was in progress and it was startup, they did
not have much documentation. Whatever documents were there they were hardly updated as new
releases were made now and then with many unplanned changes. So, it was a real challenge for us to
go ahead with project but yes we took the challenge.

Travel Tech

Our Approach

We thoroughly analyzed his requirements and based on that made complete testing plan and finally executed it successfully. Below are the highlights of whole testing process:-

Number of Resources:

Two Testers and one Test Lead – Chosen from our existing experiences testers pool and having exp. in the range of 5-9 yrs.

Test Type:

–  Functional Testing – To ensure that all functionalities worked fine in the current release.

– Smoke Testing – With every release, we needed to make sure that basic functionalities worked fine.

– Regression Testing – With every release, we needed to make sure that all previous functionalities worked fine.

 

Scope of Functional Testing:

  • End-to-End
    – Positive
    – Negative
  • UI testing

– Non Functional Testing

– Performance Testing

 

Testing Process followed based on type of testing

I. Functional Testing process followed

a) Test Case Development
b) Review of Test Cases
c) Test Case Execution
d) Bug Reporting
e) Review of Bugs Reported.
f) Verification of Bugs on new releases

II. Non-functional Testing process followed

a) Test Case Development
b) Review of Test Cases
c) Test Case Execution
d) Performance Reports
e) Performance Engineering By Development Team

Modules Covered

Customer, Operator and Admin

Tool used for Bug Reporting

BugZilla

The Result

With the experience and dedication of our team, we developed around 1700 test cases and reported 490 bugs. It took around 325 Hrs. to complete this whole testing work. We helped our client to ensure the quality of his Web and Mobile Apps. Allowed him to focus on development activities as we managed the whole testing process.

At the end, we delivered full-fledged defect log (reviewed, validated and without duplicates) along with Test Summary Report.