TDM, TDS and TCD

TDM

The Test data Management(TDM) components are used to managing the test data which are required for test execution. The data are stored same as shared database repository which is used to create the workspace, through the TDM which will be assigned to test cases during the execution. In case of SQLite, the separate instance of database is required for TDM. It enables you to view all records in your test data repositories and modify or delete selected ones. It is automatically installed as part of the Test Data Service component in the Tricentis Tosca Server setup. TDM combines Test Data Service (TDS) and test data management to allow teams to design, locate, manage, and provide test data, even in complex and hard-to-manage scenarios. The TDM component is available with the standard Tosca installation. 

TDS

TDS stands for Test Data Service, which is used for test data management in Tosca. Using TDS, we can store the dynamic test data in a shared location which is easy to read/ update by the test case. As the data stored in a shared location, it is useful to share the same dynamic data across multiple test cases. Also, we can update it without opening Tosca as it’s treated as a separate component.

TCD

In Tosca TestCase-Design section is an AddIn that enables to isolate the test data from the technical sections of test cases. So, the data and test cases are kept separately. The Tosca Test Case Design section has the capability to break our test cases into a logical structure. It is also help us to plan and design the testcases in a efficient and structured way to reduce the development and maintenance efforts.

Objects:

• Folder – The test case design folder is used to group the test sheets or classes in a logical way.
• TestSheet – TestSheet is a list of data for all possible combinations of Tosca test cases. Each data set represents one unique test case.
• Attribute – It’s referred to as the different data parameters corresponding to each application field.
• Attribute(not business-relevant) – It’s used for comment or description purposes.
• Attribute(result) – It’s used for result purposes.
• Instances Collection – It holds the Instances i.e., all possible values available for particular attribute.
• Instances – This is the value of each attribute/parameter. It can be created TestSheets, Attributes, or Class level. Instances of Testsheets are basically a test case name.
• Class – This is similar to testsheets, but it’s used for the reusable purpose. All the common data are stored here, which can be reused in multiple testsheets.
• Class reference – It’s acting as a link of Classes from Testsheets. We can create it with the drag-drop method.

Test Case Design section is performing the below activities – 

1. Create the testsheets, which is a combination of all possible test cases for any particular scenario or template. Basically, testsheets are holding the data for different combinations.
2. The concept of class in test case design approach, helps to reuse the common data across the test cases which reduce the efforts of data management.
3. With the help of instances, we can create the specific data for TestSheets, TCD Attributes, or TCD classes.
4. Create TestCase Templates and assign the Testsheets.
5. We need to instantiate or re-instantiate Templates to generate the instance test cases as per the testsheets.
6. Manage test data in testsheets and execute the instance test cases

Object hierarchies in Test Case Design:

1. A TestSheet may have Attributes, Instances, TestSteps, and class references.
2. A class may be the combinations of class Attributes and Instances.
3. Again, an Attribute can keeps further Attributes and Instances.
4. A Step can keeps more Steps and Attributes.