HOTSPOT - You need to meet the project manager's requirements for testing. What should you do? To answer, select the appropriate options in the answer area. NOTE: Each correct selection is worth one point. Hot Area:
Suggested Answer:
Box 1: Add developer placeholder. Note: The user creating the test script must document the step in the test script that the specific validation script must be run for the developers. Add developer placeholder lets the user add a placeholder step to the list of recorded steps. This placeholder step doesn't appear when the task guide is viewed, and it isn't run during maintenance of a recording. It's used only by the Regression suite automation tool (RSAT) or the X++ code generator that enables an X++ test to be created from a task recording. When the code generator creates an X++ test, it automatically adds a method stub to the generated code. The developer can then add X++ code into this method stub. The automated code will call the validation when the generated test is run at the point in the recording where this placeholder was added. Note: The project manager is concerned that a critical field must have validation scripts run against it during automated testing. The developers will be required to write the custom validation script. The user creating the test script must document the step in the test script that the specific validation script must be run for the developers.
Box 2: Task Recorder Edit Step - Note: The developers will be required to write the custom validation script.
Enriching steps in a recording - There are various options for enriching a step in a recording. For example, you can adjust the text that is associated with a step and add information about a specific step. This section describes the step enrichment capabilities that are available. To access these options, click the Edit step button on a specific step of a recording. Reference: https://docs.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/user-interface/task-recorder
Add developer placeholder
"Add developer placeholder lets the user add a placeholder step to the list of recorded steps. This placeholder step doesn't appear when the task guide is viewed, and it isn't run during maintenance of a recording. It's used only by the Regression suite automation tool (RSAT) or the X++ code generator that enables an X++ test to be created from a task recording. When the code generator creates an X++ test, it automatically adds a method stub to the generated code. The developer can then add X++ code into this method stub. The automated code will call the validation when the generated test is run at the point in the recording where this placeholder was added. " https://learn.microsoft.com/en-us/dynamics365/fin-ops-core/dev-itpro/user-interface/task-recorder
On question 2: It seems like source control in DevOps - or configuration control in RSAT to control whether test scripts are modified or overwritten - seems like much better choices. In fact, I'm not quite sure I understand why they say its Task Recorder Edit Step, or what that would indeed do.
Box 2 is incorrect I believe. The Required control being referred to is described as "The project manager wants to put a control in place to ensure that once the automated testing is established the test scripts are not modified or overwritten." For this, don't we need to look to Azure DevOps settings?
Agree. Answer for box 2 shouldbe B) Azure DevOps settings
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Newb007
1 year, 5 months agoHelenaKaiser
1 year, 9 months agoKSharp
1 year, 11 months agoVenloCity
11 months, 3 weeks ago