Testing types

Short description

 Results

1. Standard: detection of mismatches in expectations and interpretations of the product requirements as well as  cyclic  Improvement of the requirements quality (correctness, completeness and adequacy, unambiguity, consistency)
2. Specific for SharePoint:  requirements analysis and review taking into account the peculiarities of the architecture, configuration and structure of SharePoint (for ex. the usage of standard SharePoint Search, validation, special symbols, etc.). As a result QA suggests some enhancements to increase the flexibility and configurability of the system.

• Get recommendations for improving flexibility and convenience of the system.

• Improve the quality of the future product.

• Lower the development and testing costs and   reduce product time of delivery by minimizing expensive rework in case of requirements-related defects.

1.  Detection of functional and GUI defects (testing against business requirements, sketches, mock-ups and other project documentation) as well as finding configuration errors (for ex., unacceptable quality of the functionality can be forced not by problems in code but incorrect system configuration)
2. Detailed GUI testing to ensure that the application looks professional, and is implemented in the uniform style. It is not so critical for standard SharePoint objects but very important for number of custom grids, forms (search, workflow), navigation trees, and different branding schemes.
3. Administrative Guide testing. It is installation process testing in accordance with the Guide the system is deployed with. A QA engineer checks if there is enough information to configure the system properly and  whether the system works correctly under default configuration. This testing type is very important in case the system is to be deployed in geographically-distributed organization because the Customer will need to install and reinstall the system several times.

• Identify the functional and GUI defects and improve product quality quickly and in time.

• Make appropriate enhancements and change requests to the default configuration and Administrative Guide. It helps to avoid  blocking of the system if the deployment takes place on the customer’s side.

• Find workarounds for some configuration errors by QA engineers. If it is possible, QA Engineers are able to reduce delays in functional testing and reporting without waiting till a new version of a solution to be delivered.

Usability testing verifies that the application appeals to the target audience and meets the customer’s requirements alongside with the non-documented requirements and enhancements which are bound by usability rules and standards. It is a method of finding logical and structural errors.

Usability testing has the following objectives:

• Determine if the project allows users to easily and efficiently accomplish their tasks
• Uncover user difficulties and frustrations associated with the site
• Collect significant usability findings (including positive and negative findings) with the purpose of improving usability of the product

Performing this test is reasonable and necessary in case of testing deep customized applications based on SharePoint.

• Verification of integration with customer external systems, MS Office integrated systems (custom plug-in, add-in and etc.) and etc.
• Verification of the systems which are integrated to SharePoint as separate modules or web-parts (for example, Brava! Enterprise, payment systems).

The test results show if integration is able to provide smooth interaction of integrated systems taking into account various systems’ constraints and peculiarities.

There can be different goals of migration testing which depends on the migration type:

1. Verifying that the projects migration is successful
2. Checking the process of Projects migration testing from custom DMS to SharePoint products 
3. Testing of the developed Custom Migration Tools to ensure that it can support the migration process

• Identify defects found during migration process. As a result, it reduces the number of errors and mistakes during real migration.

• Increase the quality of the Custom Migration Tool (as a result of testing migration errors handling, GUI issues, etc.)

1. Checks different configurations of Standard SharePoint groups and their rights
2. Tests functionality under custom groups  and permissions
3. Check internal (intranet) and external (external site) access points to SharePoint based application.

• Whether Security Policy is carried out (all users can go through their business process and limited users are restricted from doing some actions, etc.)
• If a system can be accessed from the outside (authentication, correct pages redirection, etc. testing) and external users can operate with functionality.

• Frequent or time-consuming functional test case generation
• Hard-to-reproduce scenario generation
• Data generation
• Iterative mechanisms check
• Regressions detection.

• Reduces manual testing efforts for re-testing stable functionality (regression testing)
• Allows more frequent build delivery and minimal QA of these builds
• Reduces efforts on multi-platform and multi-browsers testing
• Minimizes routine testing operations and replace them with automated test.

Performance testing