Posted: 5 Oct 2020 11:45 EDT Last activity: 13 Oct 2020 2:00 EDT
Add Assertion on any step: Scenario Based Testing
Can someone explain in details about assertion and below features whenever we edit any step within a test case on portal or from DEV studio
1. Select Complete Task (Menu) : It has captured values ; what will happen if we edit and change this
UI attributes: we have tooltip, value, label and other dropdown values ; role of each dropdown value
4.Advanced; what is custom selector?
Q> What will be the difference if we change the default value(UI attribute) and how it will impact if we go and add assertion and pick any random value as per the selected field from the dropdown.For e.g. if dropdown label while recording is "TEST". a)What will happen if we make changes to default value as "TEST2"?
b) what will happen if we add an assertion and select label and change the value to "TEST2" whereas "TEST" is also there as default value
On a similar note can someone explain for other values considering above question
***Edited by Moderator Marissa to update Platform Capability tags****
1. Select Complete Task (Menu) : --> this is a default level. Changing this value wont make testcase failure. For each test step, this step level gets generated.
"Scenario Testing" in general we work around different controls (for example pxMenu / pxLink / pxDropDown etc). So, each step of the testcase also captures state for a particular control. From your question this line - [Select Complete Task (Menu)], which looks to me a Menu Control you have captured.
Now, coming to assertion, we assert few features of the underlying control itself. So, tooltip, value, label and other dropdown options ,they belong to that control itself. From the section layout, if you open the control you will get to see these. And yes, for different controls these options are also different.
3. Actions -> Any value change on a textInput control or any click events on the control is captured and displayed in this section. But user cannot change other events, but they can update the values they have entered in a textInput type control.
4. Custom Selector : The DOM element locating the control(for that step), is captured by default during recording. But, if test writer specify any other CSS selector to locate that control, they that gets precedence and during playback, that is used.
For the 2 scenarios , test step will fail. As during play back, the original control wil have TEST, but the expected value is TEST2, so it will fail.