Image Based Testing-IndicThreads-Q11
Download as PPT, PDF0 likes388 views
Image-based testing (IBT) is an alternative automation approach that relies on images rather than objects. It allows testing applications where objects are not recognized by traditional tools. IBT interacts directly with the visual display by finding and interacting with graphics. Tests are developed by capturing images, mapping logical names, and writing scripts similar to object-based testing but using image recognition strings instead of object properties. Challenges include needing images for all variations in display configurations and themes.
![SAFS Image-Based Recognition Syntax Component is an image inside another image. [BulletsItem] BulletsItem =“Image=pathTo\BulletsItemImages” ArrowButton=“Image=pathTo\ArrowButtonImages” Component is inside bounds defined by other images. [OfficeWin] OfficeWin =“Image=pathTo\OfficeAnchorImages; _ ImageRight=pathTo\OfficeCloseIcons” CenterText=“Image=pathTo\CenterTextImages” BulletsItem ArrowButton OfficeWin CenterText](https://image.slidesharecdn.com/7381784/85/Image-Based-Testing-IndicThreads-Q11-13-320.jpg)
![How to automate using IBT Test Development for IBT is the same Fewer Component Functions supported. Tests and commands look the same as OBT. App Map development is mostly the same Recognition strings are VERY different. It’s all about images, not components. e.g. IExplorer App Map Entry:[IExplorer] IExplorer="Image=<imagepath>"](https://image.slidesharecdn.com/7381784/85/Image-Based-Testing-IndicThreads-Q11-14-320.jpg)
![Sample Application Map [SampleApplication] SampleApplication="Image=c:\Images\AnchorImage.bmp;ImageR=c:\Images\CloseIcon.bmp" ButtonMinimize="Image=c:\Images\MinIcon.bmp" ButtonMaximize="Image=c:\Images\MaxIcon.bmp" ButtonClose="Image=c:\Images\CloseIcon.bmp"](https://image.slidesharecdn.com/7381784/85/Image-Based-Testing-IndicThreads-Q11-18-320.jpg)
Image Based Testing-IndicThreads-Q11
- 1. Image Based Testing- application technology independent automation Girish Kolapkar SAS R&D (India)
- 2. Agenda: What exactly IS Image-Based Testing (IBT)? OBT vs IBT Thinking and Testing Differently with IBT Developing IBT Tests and App Maps SAFS Image-Based Recognition Syntax How to automate using IBT Image Manager Tool Sample Application Map And Script
- 3. Agenda: Dealing with Variations in the IBT Environment Dealing with NLS Testing in an IBT Environment Challenges Demo Q & A
- 4. What exactly IS Image-Based Testing? Strictly “What You See is What You Get” (WYSIWYG) Interaction with the visual display of the screen Testing based on finding and interacting with graphics on the screen Automation is driven through keyboard and pointer events Test technologies partially or not supported by existing tools E.g Legacy Applications (Xterm application),Flash Applications, GUI on Unix
- 5. What exactly IS Image-Based Testing? An alternative when items are not recognized at all by existing tools Independent of any underlying application technology The antonym or opposite of Object-Based Testing.
- 6. What exactly IS Image-Based Testing? Image Based Testing Tool Operating System Application Under Test Display Buffer Mouse pointer events/ keyboard events queue
- 7. OBT vs IBT Object-Based Testing Ideal for automating PC hosts Performance: slower than IBT Can automate supported technologies only Can produce reliable & robust scripts(time tested) Wide range of functions available to use Image-Based Testing Ideal for Applications which OBT can’t support or limited support e.g. GUI on non PC hosts, legacy applications Performance :faster than OBT Can automate virtually anything that can be displayed on the screen Needs to be proved\improved after extensive usage Limited verifications
- 8. Thinking and Testing Differently for IBT Object-Based Testing deals with real components. Image-Based Testing deals with images. IBT doesn’t look for any object hierarchy Application Map or Object Map is defined by images not by properties All possible Image variations needs to be stored
- 9. SAFS Image-Based Recognition Syntax SAFS keeps concept of Components in Windows A “component” can be: an image inside another image. an image inside the bounds of other images.
- 10. Component as an Image inside another Image Finding the right Arrow in a Sea of Matching Arrows Locate the Unique Anchor that contains the Target Locate the Target within the Anchor Component Function call: BulletsItem, ArrowButton, Click A “component” can be: an image inside another image. an image inside the bounds of other images. BulletsItem ArrowButton
- 11. Component as an Image inside the bounds defined by other Images Finding a Target inside the bounds from a single image Component Function call: OfficeWin, NewSlide, Click A “component” can be: an image inside another image. an image inside the bounds of other images. OfficeWin NewSlide
- 12. Component as an Image inside the bounds defined by other Images Find a Target inside the bounds defined by multiple images Component Function call: OfficeWin, CenterText, Click A “component” can be: an image inside another image. an image inside the bounds of other images. OfficeWin CenterText
- 13. SAFS Image-Based Recognition Syntax Component is an image inside another image. [BulletsItem] BulletsItem =“Image=pathTo\BulletsItemImages” ArrowButton=“Image=pathTo\ArrowButtonImages” Component is inside bounds defined by other images. [OfficeWin] OfficeWin =“Image=pathTo\OfficeAnchorImages; _ ImageRight=pathTo\OfficeCloseIcons” CenterText=“Image=pathTo\CenterTextImages” BulletsItem ArrowButton OfficeWin CenterText
- 14. How to automate using IBT Test Development for IBT is the same Fewer Component Functions supported. Tests and commands look the same as OBT. App Map development is mostly the same Recognition strings are VERY different. It’s all about images, not components. e.g. IExplorer App Map Entry:[IExplorer] IExplorer="Image=<imagepath>"
- 15. How to automate using IBT Capture images in supported formats BMP, GIF,JPEG,PNG,TIFF etc. Map logical names for the "window" and the "component" in the application map Write test records\scripts same as OBT Execute records using SAFSDRIVER Review the results
- 16. Image Manager Tool Tool to facilitate image captures Command to launch java org.safs.image.ImageManager
- 17. Enhancements BitTolerance|BT= Optional. Specifies the integer percentage (1-100) of image bits or pixels that must match for an image to be considered a successful match. The default is, of course, 100. This means ALL pixels must match unless some other BitTolerance is specified. Samples: IExplorer="Image=<imagepath>;BitTolerance=70" IExplorer="Image=<imagepath>;ImageR=<imagepath>;BT=75"
- 18. Sample Application Map [SampleApplication] SampleApplication="Image=c:\Images\AnchorImage.bmp;ImageR=c:\Images\CloseIcon.bmp" ButtonMinimize="Image=c:\Images\MinIcon.bmp" ButtonMaximize="Image=c:\Images\MaxIcon.bmp" ButtonClose="Image=c:\Images\CloseIcon.bmp"
- 19. Sample Test Records C SetApplicationMap Demo.MAP C LaunchApplication SampleApplication "c:\safs\samples\Dotnet\DotNetApp\WinDemo.exe" C WaitForGUI SampleApplication SampleApplication 15 T SampleApplication SampleApplication GetGUIImage c:\OutputImage1.jpg T SampleApplication SampleApplication RightClick T SampleApp SampleApp InputKeys "x" T SampleApplication SampleApplication GetGUIImage c:\OutputImage2.jpg T SampleApplication ButtonClose Click
- 20. Dealing with Variations in the IBT Environment 32-Bit, 24-Bit, 16-Bit Color Depth and Resolution Themes and Schemes Platform and Version Image and Icon Variations Multiple images are necessary if the target image is different in different environments Identify and Store Item Variations in a Directory
- 21. Dealing with NLS Testing in an IBT Environment Same as any Recognition String handling for NLS: Item1=pathTo\{^SHARED_DIR}\targetImages Item2=pathTo\{^LANG_DIR}\targetImages Images will have to be captured and transferred if there is a language dependency
- 22. Challenges It’s all about images Require to capture all possible image variations Precise\Reliable\Unique Images Display configurations Time consuming test development Verification Image verification only Can’t verify component properties Can’t extract data from application under test Themes and Schemes Platform and Version Image and Icon Variations Identify and Store Item Variations in a Directory
- 23. Demo What the IBT demo does Launch Sample Application Perform few interactions Close Review the results
- 24. Q&A
- 25. Thanks References : SAFS Image-Based Recognition http://safsdev.sourceforge.net/sqabasic2000/SAFSImageBasedRecognition.htm
Editor's Notes
- #5: Explain how IBT is all about graphics on screen and its all about images. There might be many other challenging UI technologies which are prevalent in market but do not have good tool support for testing. IBTs score a point here.
- #6: As automation inputs and outputs are produced and consumed on the OS level, the application technology becomes irrelevant and it can automate any GUI application which is displayed on screen.
- #8: Along with this, the ease associated with doing trivial operations like reading a text, verifying enabled/disabled state, selecting from a dropdown or grid etc. helps OBT score a good point when compared to IBT. IBTs offer an alternative here since they are UI technology neutral.
- #13: When seeking a &quot;window&quot; mapping the entire screen is searched for this image. When seeking a &quot;component&quot; mapping the search area is limited to the area of interest found for the &quot;window&quot; mapping. The bounds of the area of interest can be expanded by using the optional ImageR and ImageB items described below.
- #16: It is important to note that images must be saved in a format that provides no-loss of pixel information. Stored images must be able to match with 100% picture quality the image snapshots that will be retrieved from the screen. While &quot;BitTolerance&quot; discussed above allows for some degree of comparison fuzziness, it will usually not be able to compensate for stored images that cannot reproduce 100% picture quality due to excessive compression or intentional loss of pixel information.
- #17: Images stored for a particular Display typically work for most or all screen resolutions on that Display. This is an issue that each Display is configured for different levels of data compression. Bitmaps stored for the Normal Display have no data compression and no loss of image information. The displayed image for the Remote displays is usually compressed--intentionally removing image information. Because of this, Normal Display images usually will not match Remote Display images. To compensate for this, it is highly recommended that recognition images always be captured in the display mode that will be used for runtime testing. For example, if you know all testing will be done via Remote Desktop sessions, then it is best to have all recognition images captured and prepared during Remote Desktop sessions.
- #18: It is important to note that images must be saved in a format that provides no-loss of pixel information. Stored images must be able to match with 100% picture quality the image snapshots that will be retrieved from the screen. While &quot;BitTolerance&quot; discussed above allows for some degree of comparison fuzziness, it will usually not be able to compensate for stored images that cannot reproduce 100% picture quality due to excessive compression or intentional loss of pixel information.
- #19: It is important to note that images must be saved in a format that provides no-loss of pixel information. Stored images must be able to match with 100% picture quality the image snapshots that will be retrieved from the screen. While &quot;BitTolerance&quot; discussed above allows for some degree of comparison fuzziness, it will usually not be able to compensate for stored images that cannot reproduce 100% picture quality due to excessive compression or intentional loss of pixel information.
- #20: It is important to note that images must be saved in a format that provides no-loss of pixel information. Stored images must be able to match with 100% picture quality the image snapshots that will be retrieved from the screen. While &quot;BitTolerance&quot; discussed above allows for some degree of comparison fuzziness, it will usually not be able to compensate for stored images that cannot reproduce 100% picture quality due to excessive compression or intentional loss of pixel information.
- #21: imagepath can be the full path to a single image or to a directory containing multiple images. Multiple images are necessary if the target image is different in different environments. For example, on different platforms, or different versions of the application or operating system. The framework will search the screen for each of the images in the directory until it finds the match.