The Sikuli IDE provides you with your primary interface for working with and executing Sikuli scripts. Here, we can get a quick overview of the components of the UI:
The toolbar contains buttons for common actions in Sikuli. From left to right these are:
• Take screenshot: This is used when capturing portions of the screen for use in your scripts
• Insert image: This lets you select an existing image to search for on the screen
• Create Region: This lets you create a region on the screen to reference in your scripts
• Run: This will execute your script
• Run in slow motion: This will execute your script in slow motion, which can be extremely handy for debugging Sikuli scripts
• Find: This lets you search for text in your Sikuli script code
The bar on the left provides a list of common commands and their arguments. You can double-click on any of these commands, and they will be inserted into your script. For example, if you double-click on the exists() command, it will insert it into your script, and immediately put Sikuli into the capture mode to make a screen selection. This selection will then be inserted into the exists() command in your script.
The editor provides you with a way to create and change your scripts. For every open script there is a tab. Generally speaking, you'll want to use Sikuli's editor for writing scripts, since it provides you a good way to see what your scripts are doing and interact with the screenshots. The editor has a few quirks, but considering the additional features it provides, specific to Sikuli (and the need to synchronize multiple files in the underlying file format), it is an important tool for working with Sikuli.
Finally, there's a small console at the bottom of the UI, which provides feedback about running scripts. If your script generates console output or fails due to an error, it will be noted here.
Sikuli provides an excellent platform for automated testing of applications. Through the use of screenshots and simple commands, it makes it much easier for non-programmers to create tests, and provides a good introduction for testers to the greater power that scripting provides. Testers can start out simply, and add more complexity as they become familiar with the tool and need to expand their ability to do more complex testing.
It is possible to integrate Sikuli with any tools of this kind that support access via some sort of web-based API.
The toolbar contains buttons for common actions in Sikuli. From left to right these are:
• Take screenshot: This is used when capturing portions of the screen for use in your scripts
• Insert image: This lets you select an existing image to search for on the screen
• Create Region: This lets you create a region on the screen to reference in your scripts
• Run: This will execute your script
• Run in slow motion: This will execute your script in slow motion, which can be extremely handy for debugging Sikuli scripts
• Find: This lets you search for text in your Sikuli script code
The bar on the left provides a list of common commands and their arguments. You can double-click on any of these commands, and they will be inserted into your script. For example, if you double-click on the exists() command, it will insert it into your script, and immediately put Sikuli into the capture mode to make a screen selection. This selection will then be inserted into the exists() command in your script.
The editor provides you with a way to create and change your scripts. For every open script there is a tab. Generally speaking, you'll want to use Sikuli's editor for writing scripts, since it provides you a good way to see what your scripts are doing and interact with the screenshots. The editor has a few quirks, but considering the additional features it provides, specific to Sikuli (and the need to synchronize multiple files in the underlying file format), it is an important tool for working with Sikuli.
Finally, there's a small console at the bottom of the UI, which provides feedback about running scripts. If your script generates console output or fails due to an error, it will be noted here.
Sikuli provides an excellent platform for automated testing of applications. Through the use of screenshots and simple commands, it makes it much easier for non-programmers to create tests, and provides a good introduction for testers to the greater power that scripting provides. Testers can start out simply, and add more complexity as they become familiar with the tool and need to expand their ability to do more complex testing.
It is possible to integrate Sikuli with any tools of this kind that support access via some sort of web-based API.
No comments:
Post a Comment