The integration tests are structured in fixtures. Each fixture holds a set of tests and a tear down method. For more information about each element, read the sections below.
The test fixtures hold the tests. You can use multiple fixtures and group your tests depending on the functionality they cover. Each fixture is represented by a class. To create a fixture, perform the following:
The tests are represented by methods that contain the logic that you want to test. To create a test method, you must perform the following:
NOTE: You can mark a test method with the Ignore attribute. When you run an entire fixture or all of the tests, the tests marked with this attribute will get skipped.
EXAMPLE: For an example containing tests, see SimpleTests.cs in Sitefinity SDK: documentation-samples on GitHub.
The tear down method is executed after each test. It is optional. Typically you use it only when you have made some permanent changes to the testing environment and you want to bring them back once the test has been executed. For example if you have created a document library during your test and you want to remove it once the test has been executed, you implement the logic for removing the document library in the tear down method. To create a tear down method, perform the following:
EXAMPLE: For an example containing tests, see TearDownClass.cs in Sitefinity documentation-samples on GitHub.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity