New Year Sale 2026! Hurry Up, Grab the Special Discount - Save 25% - Ends In 00:00:00 Coupon code: SAVE25
Welcome to Pass4Success

- Free Preparation Discussions
Mail Us support@pass4success.com
Location US
Mob_nav_barsMENU

Microsoft MB-500 Exam - Topic 4 Question 26 Discussion

Actual exam question for Microsoft's MB-500 exam
Question #: 26
Topic #: 4
[All MB-500 Questions]

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.

Show Suggested Answer Hide Answer
Suggested Answer: A, C, D

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

by Kiley at May 05, 2022, 09:07 AM

Limited Time Offer

25%

Off

Get Premium MB-500 Questions as Interactive Web-Based Practice Test or PDF

Contribute your Thoughts:

0/2000 characters
Submit Cancel
Merissa
4 months ago
Just to clarify, Test Property and Owner are definitely correct!
upvoted 0 times
...
Janae
4 months ago
I thought EntryPoint was for something else, not unit tests.
upvoted 0 times
...
Tuyet
4 months ago
Wait, isn't TestFilter also a valid option?
upvoted 0 times
...
King
5 months ago
Totally agree, those are the right attributes!
upvoted 0 times
...
Tamesha
5 months ago
You can use Test Property, Owner, and Priority for unit tests.
upvoted 0 times
...
Lovetta
5 months ago
I’m pretty confident that TestFilter isn’t one of the attributes we use for creating a unit test class.
upvoted 0 times
...
Floyd
5 months ago
I’m a bit confused about EntryPoint; I don’t recall it being used for unit tests. Maybe it’s for something else?
upvoted 0 times
...
Titus
5 months ago
I practiced a similar question where we had to identify attributes for unit tests, and I feel like Priority was one of them.
upvoted 0 times
...
Olene
5 months ago
I think I remember that we can use attributes like Test Property and Owner, but I'm not entirely sure about the third one.
upvoted 0 times
...
Kris
5 months ago
This looks like it's testing my knowledge of reinsurance accounting. I'll draw on what I know about the different premium categories and try to logically eliminate the incorrect answers.
upvoted 0 times
...
Alica
5 months ago
Okay, let me think this through. Negative risks are the potential downsides or threats to the project, so they would need to be recorded somewhere. The risk register seems like the most logical place for that. I'll go with A.
upvoted 0 times
...
Mozell
5 months ago
Okay, I think I've got it - A shows the quota attainment, B gives the forecasting details, and E enables the quota display. That should cover the main ways to track the sales goals.
upvoted 0 times
...
Casie
5 months ago
This question seems straightforward, but I want to make sure I understand the details correctly before attempting to solve it.
upvoted 0 times
...

Save Cancel