Quality Assurance

With over 3 years of experience in software testing projects at some of the fortune 500 companies, we can boast of our team who can walk-in at any point of an on-going project and deliver right services to exceed client satisfaction. Our team is a mix bag of manual and automation testing personnel who have the exposure of working with clients of diverse industry.

Types of Testing

  • Black box testing – Internal system design is not considered in this type of testing. Tests are based on requirements and functionality.
  • White box testing – This testing is based on knowledge of the internal logic of an application’s code. Also known as Glass box Testing.
  • Unit testing – Testing individual software components or modules.
  • Incremental integration testing – Bottom up approach for testing i.e continuous testing of an application as new functionality is added. Done by programmers or by testers.
  • Integration testing – Testing of integrated modules to verify combined functionality after integration.
  • Functional testing – This type of testing ignores the internal parts and focus on the output is as per requirement or not.
  • System testing – Entire system is tested as per the requirements.
  • End-to-end testing – Similar to system testing, involves testing of a complete application environment in a situation that mimics real-world use.
  • Sanity testing – Testing to determine if a new software version is performing well enough to accept it for a major testing effort.
  • Regression testing – Testing the application as a whole for the modification in any module or functionality.
  • Acceptance testing -Normally this type of testing is done to verify if system meets the customer specified requirements.
  • Load testing – It’s a performance testing to check system behavior under load.
  • Stress testing – System is stressed beyond its specifications to check how and when it fails.
  • Performance testing –To check whether system meets performance requirements.
  • Usability testing – User-friendliness check. Basically system navigation is checked in this testing.
  • Install/uninstall testing – Tested for full, partial, or upgrade install/uninstall processes on different operating systems under different hardware, software environment.
  • Recovery testing – Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.
  • Security testing – Can system be penetrated by any hacking way. Testing how well the system protects against unauthorized internal or external access.
  • Compatibility testing – Testing how well software performs in a particular hardware/software/operating system/network environment and different combination s of above.

Testing Services We Offer

MTS is an outsourced service for testing related tasks across one or more projects delivering one or more applications and systems, spanning the life cycle of the software, system development and system operations.
  • Complexity reduction
  • Risk reduction
  • Competitive pricing
  • Output or transaction based compensation model
  • High quality of service

Test automation is the use of special software (separate from the software being tested) to control the execution of tests and the comparison of actual outcomes with predicted outcomes. Test automation can automate some repetitive but necessary tasks in a formalized testing process already in place, or add additional testing that would be difficult to perform manually.

There are many approaches to test automation; our approach:

Code-driven testing: The public interfaces to classes, modules or libraries are tested with a variety of input arguments to validate that the results that are returned are correct.

GUI testing: A testing framework generates user interface events such as keystrokes and mouse clicks, and observes the changes that result in the user interface, to validate that the observable behavior of the program is correct.

API driven testing: A testing framework that uses a programming interface to the application to validate the behavior under test. Typically API driven testing bypasses application user interface altogether.

Functional testing is a (QA) process and a type of black box testing that bases its test cases on the specifications of the software component under test. Functions are tested by feeding them input and examining the output, and internal program structure is rarely considered (not like in white-box testing). Functional testing usually describes what the system does.
We provide:

  • Smoke testing
  • Sanity testing
  • Regression testing
  • Usability testing

Mobile application testing is a process by which application software developed for hand held mobile devices is tested for its functionality, usability and consistency. Mobile application testing can be automated or manual type of testing

  • Functional Testing
  • Performance Testing
  • Memory Leakage Testing
  • Interrupt Testing
  • Usability testing
  • Installation testing
  • Certification Testing

The goal of Performance Testing is not to find bugs but to eliminate performance bottle necks.
Our team ensures:

  • Speed – Determines whether the application responds quickly
  • Scalability – Determines maximum user load the software application can handle
  • Stability – Determines if the application is stable under varying loads

Complete testing of a web-based system before going live can help address issues before the system is revealed to the public:

  • Browser compatibility
  • Operating System compatibility
  • Windows application compatibility where required
  • Web security testing
  • Focus on meeting business needs
  • End-to-end ownership
  • Committed to end user satisfaction
  • Overall reduction in operational cost
  • Pool of shared resources for effective utilization of time and resources and reduce cost
  • Process driven methodology