Testing in DTML code base

We have two types of tests Unit Tests and Deployment verification tests. Both using similar infrastructure but with different goals and means.

Unit tests

Unit testing is the process of writing code to test the behavior and functionality of your system. The primary goal of unit testing is to take the smallest piece of testable software in the application, isolate it from the remainder of the code, and determine whether it behaves exactly as you expect. Each unit is tested separately before integrating them into modules to test the interfaces between modules. Unit testing has proven its value in that a large percentage of defects are identified during its use. Uni tests are defined by using Test Methods on Testcase Classes and located in DTML.UnitTests project.

It is important to keep each test case is independent from the others; Double objects like stubs, mock or fake objects1 as well as test harnesses can be used to assist testing a module in isolation. The first one is setup test or arrange test, Act test or execute unit test and Assert means verify test result with expected results. The concept of three "A"s are given below.

Arrange: This is the first step of a unit test application. Here we will arrange the test, in other words we will do the necessary setup of the test. For example, to perform the test we need to create an object of the targeted class, if necessary, then we need to create mock objects and other variable initialization, something like this.

Act: This is the middle step of a unit step application. In this step we will execute the test. In other words we will do the actual unit testing and the result will be obtained from the test application. Basically we will call the targeted function in this step using the object that we created in the previous step.

Assert: This is the last step of a unit test application. In this step we will check and verify the returned result with expected results. Unit test are ran as part of the build process.

DTML Unit Test example

[TestMethod]
        public void HomeController_VerifyProfanityIsPassing()
        {
	     // Assign variables and create needed instances
            HomeController controller = new HomeController();
            UserModel testModel = new UserModel();
            testModel.FirstName = "FirstName";

	     // Act 
            var result = controller.noProfanities(testModel);

	     //Assert
            Assert.IsTrue(result);
        }

Integration (Functional) tests

In opposite to unit tests functional testing tests a slice of functionality of the whole system. While use same test harness the meaning and implementation of tests are very different. Integration test are running as validation step in each environment. Integration tests are simulating user navigation between pages by using CookieAwareWebClient.

As such integration tests have following structure:

Step 1. Navigate to login page

var indexPage = ReadURL(environmentHost + $"/Account/Login", out cookies);

Step 2. Read token

var token = GetRequestVerificationToken(indexPage);

Step 3. Login

client.UploadValues(…)

Step 4. Verify functionality of the page