Software QA / Testing

BESTSOFT Consulting follows interactive V model for software testing process. We have modified the conventional V model to make it compatible with new age iterative software development processes like Rational Unified Process, Agile Development Process and Extreme Programming.

Software Testing - Process Overview

BESTSOFT Consulting understands that the Software Testing is a key process in ensuring the quality software especially in the software outsource model.

The conventional V model was suited for Waterfall software development process. Iterative V Model is what we follow at BESTSOFT Consulting. Iterative test process is best suitable for projects where development is done by one team and testing is done by an independent team.

Iterative test process consists of many iterations and every iteration consists of phases.

Each iteration has one release and all phases of V model are executed in one iteration. This leads to better quality releases as changes done in one iteration are tested and complete system is tested again foe any break point that crept in because of implementation in current iteration in every iteration, percentage activity of phases is decided based on specification change scope.

Phases of Testing

At BESTSOFT Consulting we perform different phases of testing like component testing, interface testing, system testing, release testing and acceptance testing at different stages of development process, thus ensuring that our customer product launched is bug-free and it meets the requirements.

Component Testing - Component Design

• This first test level is sometimes called Module Testing.
• It checks whether each feature specified in the "Component Design" has been implemented in the component or not.

Interface Testing - System Design

• Done after each components have been checked individually using component testing
• The components are then integrated and tested for faults
• Interface Testing also focuses on how components should communicate with each other, as specified in the "System Design".

System Testing - System Specifications

• Carried after the development of the entire system
• It is tested against the "System Specification" to check if the system is meeting requirements and has all features required.
• Not only the individual parts are checked, but the system is also checked as a whole.
• Involves tests for verification of all the functional and non-functional requirements.
• Non-functional requirements include:
  • Performance - Are the performance criteria met?
  • Volume - Can large volumes of information be handled?
  • Stress - Can peak volumes of information be handled?
  • Documentation - is the documentation usable for the system?
  • Robustness - Does the system remain stable under adverse circumstances?
  • And others, depending upon the type of the system

Acceptance Testing - Requirements

• Done to see if the required system meets the requirements.
• Different from the system testing as system testing is tested against specifications whereas acceptance testing is done against the requirements and hence is done by the customer.
  
  BESTSOFT Consulting provides tools and training to our clients to help them in successfully performing acceptance testing.

Release Testing - Business Cases

• Seeing if the new or changed system will work in the existing business environment
• Mainly this means the technical environment, and checks concerns such as:
  • Does it affect any other system running on the hardware?
  • Is it compatible with other systems?
  • Does it have acceptance performance under load?

BESTSOFT Consulting designs the system, keeping in mind its compatibility with the hardware. Our computer operation team is involved in the starting of the project who study the impact the new system may have on the business environment