-
Module 1: E-COMMERCE TECHNICAL OVERVIEW
-
Module 2: DEVELOPMENT ENVIRONMENT
-
Module 3: BRANDING THE E-COMMERCE SITE
-
Module 4: ECOMMERCE WEB PARTS
-
Module 5: SEARCH CONFIGURATION AND CUSTOMIZATION
-
Module 6: COMMERCE RUNTIME SERVICES
-
Module 7: TESTING, DEPLOYMENT AND VERSIONING OF ECOMMERCE SITE
Lesson 1: Testing Considerations
Testing Considerations
Testing Considerations : This topic covers the different stages for testing a custom SharePoint application.
Lesson Objectives
To understand the different test strategies that can be taken for doing Ecommerce development and customization.
Testing Overview
Testability is one of the primary design goals for any application. The following diagram from the Acceptance Test Engineering Guidance shows the testing layers.
Layers for Testing
Each type of test has a distinct purpose. They are the following:
Unit testing: Unit tests are written by developers and run under a unit testing framework, such as Microsoft Visual Studio Team System or NUnit. Unit tests isolate and verify discrete units of program logic. They isolate the logic by replacing dependencies on the run-time environment, such as SharePoint, with test-provided substitutes. Isolation allows unit tests to run quickly, and developers can run unit tests frequently.
Integration testing: Integration tests differ from unit tests in that the code under test is not isolated. Integration tests are written by developers or testers. They run in a unit testing framework.
Acceptance testing: Acceptance tests consist of multiple steps that represent realistic usage scenarios of the application as a whole. These tests verify that an application meets the needs of the intended users. Their scope includes usability, functional correctness, and performance. Generally, test engineers create these tests.
Unit Testing with Mock Objects and Automate Unit Testing for UI Testing
If the application references external components and if those components are not available for testing, unit testing can be achieved by creating mock objects for the external components. Mock objects are instances of test-provided classes that simulate the behavior of external components. Mock objects isolate the application code for testing. They create conditions that are otherwise difficult to produce, such as a disk full exception.Mock objects can be implemented in the following three ways for unit testing