QUALITY ASSURANCE
(QA) & TESTING:
Approach & Methodology:
QA Testing Methodology is precisely defined at
MachroTech. Project Management, Maintenance of Time Schedules, Quality
Assurance, and Software Engineering are some of the key areas we
focus on in the Software Development Life Cycle process. Our exhaustive
Methodology ensures thorough and effective QA Testing of the software
products and applications.
- Data Integrity Testing
Data integrity testing, a key component of QA testing, has to
do with verifying the reliability of data procurement and storage
methods in order to ensure that the data obtained is in the required
format, and that it is reliable and consistent with the data expected
to be present in the database. Data Integrity Testing also ensures
that all relevant information is stored in a timely manner, thus
avoiding data loss, which has the potential to prove catastrophic
to a business. Parameters can also be customized as per client
requirements for the data integrity testing during the setup phase.
- Functionality Testing / Defect Analysis
A thorough review of a client's application needs and of their
existing systems helps us develop the Functionality tests. These
tests are performed by MachroTech on the basis of our systematic
methodology for Internal Documentation, Reporting, and Resolution
of defects and bugs detected during the various testing processes.
The analysis of these defects and bugs are carefully documented
to provide our clients with:
- A Complete description of the bug/defect and the process
of reproducing it
- A clear assessment of the usability of the product and its
relation to the business objectives
- Critical data and information needed by the developers involved
in debugging. This involves a cost/benefit tradeoff.
- Performance Testing
Performance testing involves testing the product on the basis
of the following criteria and other Custom criteria as required
by the Client:
- Stress Testing
In Stress Testing, the parameters typically tested are: Storage,
Computing Time, Communication Capacity, and Database Recovery
Time. This process drives the system to the very limits of
its endurance in order to determine what features in the application
design can fail during implementation. The features that do
fail can turn out to be defects capable of causing disastrous
failure.
- Availability Testing
Availability testing involves testing the reliability of the
network, database processor, memory, etc. This involves testing
the capability to have the support for critical data required
by the applications to be up and running in minimum standard
conditions. All the architectural components that need to
be available are also made sure to be present and functional.
- Response / Throughput Testing
Response / Throughput testing is used to test the load-bearing
capacity of the system and to measure the response time and
throughput of the various components of the system.
- Compatibility Testing
Compatibility testing addresses concerns regarding a product’s
capability to interface with other software and hardware. MachroTech
is equipped to test Client products across a varied range of software
and hardware platforms to evaluate the related issues involved
in Compatibility Testing.
- Usability Testing
Usability testing is concerned with evaluating a system’s ease
of use and the level of convenience it provides to non-technical
people to enable them to utilize the various tools and functionalities
offered by the system. This helps users derive the maximum benefit
from the system. Usability Testing further entails detailed analysis
of the navigation system, the user interfaces, etc. General Usability
testing also involves the following:
Authentication
GUI forms and selections such as:
- Text Boxes
- Radio Buttons
- Check Boxes
- Drop Down List Boxes
- Combo Boxes
- Screen Validations / Validation Conditions
- Navigation Conditions
- Usability Conditions
- Other Generic requirements
Preferred QA Testing
Model:
Onshore / Offshore QA and Testing
MachroTech’s Global Delivery Model combines the advantage
of offshore
software development with direct control over the project
onshore. In this model our onshore business staff liaise with
our clients, while the development staff are based offshore. Clients
benefit by this model in the following ways:
- Onshore test/plan/design team in direct communication with
client development team.
- Effective communication between client and offshore team ensured.
- Time efficiency.
- Offshore team can work for more than one shift if required.
|
