MB-500 Exam: Creating Unit Test Class

Creating Unit Test Class for SysTest Framework in Visual Studio

Question

You are using the SysTest framework to test code in Visual Studio.

You need to create a unit test class.

Which three attributes can you use to create the class? Each correct answer presents a complete solution.

NOTE: Each correct selection is worth one point.

Answers

Explanations

Click on the arrows to vote for the correct answer

A. B. C. D. E.

BCE.

The SysTest framework now supports the major test attributes in the adaptor to be on par with the MSTest framework adaptor.

This includes attributes like Category, Owner, Priority, and Test Property.

Note: The Priority attribute SysTestPriority, which requires an integer value, is now available.

A priority can only be specified once, but is supported on both the class and method level, with method level taking precedence over class level.

The Owner attribute, SysTestOwner, has also been added.

This attribute was technically already supported for filtering in the Test Toolbox window, but the attribute itself was missing in X++

Similar to Priority, an owner can only be specified once and is supported on both the class and method level, with the method level taking precedence.

SysTestProperty specifies a property and a value (two strings), and can now be used in the Test Toolbox window in Visual Studio.

Test Property can be specified multiple times, and can exist on both the class and method level.

https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/perf-test/systest-filtering

Sure, here is a detailed explanation for each of the attributes that can be used to create a unit test class in Visual Studio using the SysTest framework:

A. TestFilter: This attribute can be used to specify a filter that identifies which tests to include or exclude when running tests. You can use this attribute to group tests into categories and then include or exclude categories from your test runs. The TestFilter attribute takes a string as a parameter, which can be used to specify the filter expression.

B. Priority: This attribute can be used to set the priority of a test method. Tests with higher priorities are executed before tests with lower priorities. The Priority attribute takes an integer value as a parameter, which specifies the priority of the test method.

C. Owner: This attribute can be used to specify the owner of the test method. The owner can be a user, a team, or any other entity that is responsible for the test method. The Owner attribute takes a string as a parameter, which specifies the owner of the test method.

D. EntryPoint: This attribute can be used to specify the entry point of the test method. The entry point is the method that is executed when the test is run. If this attribute is not specified, the test method is executed by default. The EntryPoint attribute takes a string as a parameter, which specifies the name of the entry point method.

E. Test Property: This attribute can be used to set additional properties for a test method. These properties can be used to provide additional information about the test method, such as the expected result or the input parameters. The Test Property attribute takes two parameters: the name of the property and its value.

To create a unit test class in Visual Studio using the SysTest framework, you can use one or more of these attributes to specify the characteristics of the test class and its methods. For example, you can use the TestFilter attribute to group tests into categories, the Priority attribute to set the order of execution, and the Owner attribute to specify the responsible team.