| At Aloha Technology, we believe that testing is a science and requires a great deal of specialized expertise. We employ modern techniques such as test automation & coverage analysis, and sophisticated methodologies in test strategy, planning, consulting, automation & execution, to produce key code stability and maturity metrics. |
| |
Outsourcing testing doesn't replace
in-house testing. We complement your own development and testing processes, seamlessly filling any gaps in your testing schedules. If you don't have your own Testing team (QA team) we can take full responsibility for your testing, integrating directly with your development team. |
 |
|
| |
| Testing at Aloha Technology can provide you with three distinct advantages: |
|
| Experienced Professionals |
| The Testing team at Aloha has expertise & experience in variety of domains and technologies. |
| |
| Cost Saving |
| We provide world-class software QA and testing services at typically less than half the cost of maintaining your own Testing & QA setup — The offshore advantage |
| |
| Standards |
| Our testing team is constantly trained on latest software Testing and QA methods and techniques. That knowledge and expertise is directly utilized in ensuring the highest quality standards needed for your software product. |
| |
| We can |
 |
Complement your existing Testing / QA staff. |
|
Provide you a complete outsourced software testing solution. |
|
Extend your testing capabilities, specifically in localization development efforts. |
|
| |
| Our range of Testing Services include: |
|
| Black Box Testing |
| The Testing team at Aloha has expertise & experience in variety of domains and technologies. |
| |
| White Box Testing |
| Based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths, and conditions. |
| |
| Unit Testing |
| Unit Testing is the first level of dynamic testing and is first the responsibility of the developers and then of the testers. Unit testing is performed after the expected test results are met or differences are explainable / acceptable. |
| |
| Parallel/Audit Testing |
| Testing where the user reconciles the output of the new system to the output of the current system to verify that the new system performs the operations correctly. |
| |
| Functional Testing |
| Black-box type of testing geared to functional requirements of an application. Testers should perform this type of testing. |
| |
| Usability Testing |
| Testing for 'user-friendliness'. Clearly this is subjective and will depend on the targeted end-user or customer. User interviews, surveys, video recording of user sessions and other techniques can be used. Programmers and testers are usually not appropriate as usability testers. |
| |
| Integration Testing |
| Upon completion of unit testing, integration testing, which is black box testing, will begin. The purpose is to ensure distinct components of the application still work in accordance to customer requirements. Test sets will be developed with the express purpose of exercising the interfaces between the components. |
| |
| System Testing |
| Upon completion of integration testing, the Test Team will begin system testing. During system testing, which is a black box test, the complete system is configured in a controlled environment to validate its accuracy and completeness in performing the functions as designed. The system test will simulate production which will occur in the "production-like" test environment and test all of the functions of the system that will be required in production. |
| |
| End-to-End Testing |
| Similar to system testing, the 'macro' end of the test scale involves testing of a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate. |
| |
| Regression Testing |
| The objective of regression testing is to ensure software remains intact. A baseline set of data and scripts will be maintained and executed to verify that changes introduced during the release have not “undone” any previous code. Expected results from the baseline are compared to results of the software being regression tested. All discrepancies will be highlighted and accounted for, before testing proceeds to the next level. |
| |
| Sanity Testing |
| Sanity testing will be performed whenever cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It will normally include a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc. |
| |
| Performance Testing |
| Although performance testing is described as a part of system testing, it can be regarded as a distinct level of testing. Performance testing will verify the load, volume and response times as defined by requirements. |
| |
| Load Testing |
| Testing an application under heavy loads, such as the testing of a web site under a range of loads to determine at what point the system's response time degrades or fails. |
| |
| Installation Testing |
| Testing full, partial, or upgrade install/uninstall processes. The installation test for a release will be conducted with the objective of demonstrating production readiness. This test is conducted after the application has been migrated to the client's site. It will encompass the inventory of configuration items (performed by the application's System Administration) and evaluation of data readiness, as well as dynamic tests focused on basic system functionality. When necessary, a sanity test will be performed following the installation testing. |
| |
| Security/Penetration Testing |
| Testing how well the system protects against unauthorized internal or external access, willful damage, etc. This type of testing may require sophisticated testing techniques. |
| |
| Recovery/Error Testing |
| Testing how well a system recovers from crashes, hardware failures, or other catastrophic problems. |
| |
| Acceptance Testing |
| Acceptance testing, which is a black box testing, will give the client the opportunity to verify the system functionality and usability prior to the system being moved to production. The acceptance test will be the responsibility of the client; however, it will be conducted with full support from the project team. The Test Team will work with the client to develop the acceptance criteria. |
| |
| Alpha Testing |
| Testing of an application when development is nearing completion. Minor design changes may still be made as a result of such testing. Alpha Testing is typically performed by end-users or others, not by programmers or testers. |
| |
| Beta Testing |
| Testing when development and testing are essentially completed and final bugs and problems need to be found before the final release. Beta Testing is typically done by end-users or others, not by programmers or testers. |
| |
