IDE script
The IDE script creation process classified into Three Steps.
1: Recording
2: Playing back
3: Saving
Step1: Recording
Selenium IDE supports to record user interactions with the browser. Thus the recorded actions term as Selenium IDE script.
Step2: Playing back
In this step, first, we have to verify track stability and success rate. Then we can execute the recorded script in IDE.
Step3: Saving
Once we have recorded a stable script, we may want to save it for future runs and regressions.
Using Common Features of Selenium IDE
Setting Execution speed
While testing web applications, we get across several scenarios action performed. Thus we must be having knowledge is enough while dealing such scenarios. So avoid failures play back these types of test scenarios.
Using Execute this command option
The IDE let have executing a single test step within the entire test script. Execute this command option use at times when we want to debug of a particular step.
Using Start point
To specify a start point within a test script to allows in IDE. The start point points to the test step from where we wish to start the test script execution. We customize the script to execute from a certain step.
Using Breakpoint
User to specify breakpoints within a test script to allow in IDE. The break points state Selenium IDE where to pause the test script. when we want to break the execution in small logical steps to execution trends.
Using Find Button
One of the most crucial features of IDE test scripts is to find and locate web elements within a web page. Web elements which have the certain respect of thing associated with them. The user challenging for making to identify a particular web element is different. the Selenium IDE provides Find button for the address of this issue.
Selenium IDE Commands
three types of Selenium IDE commands. Each of the test steps in Selenium IDE falls extending any of the following categories.
Actions
Accessors
Assertions
Actions
the Actions commands are which interact with direct application either altering. Its state or by pouring some test data.
Accessors
the commands allow storing certain values to the user-defined variable. These keep values can be later on used to create assertions and verifications.
Assertion
the Assertions are like to Accessors as they can’t interact with the application. the used to verify the present state of the application with a regard state.
Forms of Assertions:
Assert: This command makes sure the execution end in case of failure.
Verify: the IDE to support on with the test script execution even if the verification fails.
Wait For: an exact condition to arrange before executing the next test step.
These conditions are like page to be load, element to be present extending
Comments
Post a Comment