Automating Flex with QTP

Not very long ago I faced the problem of recognizing Flex objects using HP QuickTest Professional. Even with Flex 3.0.0 Add-in being installed the objects couldn't be recognized.
But it we've managed to find the reasonable solution.
So, here are the steps:
1. Launch Flex Builder
2. Create a new Flex
3. Choose it in navigator
4. Select Project > Properties > Flex Compiler
5. Type the following into the "Additional compiler arguments" field:

-include-libraries "flex_builder_dir\sdks\3.0.0\frameworks\libs\automation.swc"
"flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_agent.swc"
"flex_builder_dir\sdks\3.0.0\frameworks\libs\qtp.swc"
"flex_builder_dir\sdks\3.0.0\frameworks\libs\automation_dmv.swc"

( -include-libraries works directly with Flex Builder's directory (in Windows by default it is "C:\Program Files\Adobe\Flex Builder 3\")
6. Click OK to save changes and then once more click OK to close the project's properties
7. Compile the Flex application

Speaking of negative moments, I have to mention the major two:
1. You will have to build two versions of your application in parallel (with and without flex libs) - this is not an option for some projects
2. There is a "probe effect", although it is not too severe

P.S. Works only with IE7, Flex 3.0.0 Add-in is also required.

Also available in russian.

Mind Maps. Upgrading checklists

I think that every tester (even the rookie) knows such testing artifact as checklist. In bare outlines this artifact is a list of items that need to be checked in scope of certain functionality. In my current company it is generally used for ‘testing’ functionality that is not covered with tests and requires checking of a large amount of objects.


Some testers consider checklist to be good as is – in most cases it’s a rich text file with or without hierarchy that lists all items that are mandatory to be checked in scope of the functionality.

Others are always looking for an opportunity to improve some activities in their work processes. Using Mind Maps as an upgrade for checklist can be considered as such improvement. When using a mind map you represent the items to check in the form of diagram built around the main idea (which is your functionality to be tested) that shows the connections between objects (your check items).


By using a mind map you can make the checking process more transparent, vivid and descriptive. You can focus on a specific part of functionality by collapsing the map branches you are not working on at the moment. The diagram makes the checking progress/status obvious (e.g., using accent colors for: pass, fail, not ran, blocked, etc).


When it comes to choosing tools for mind mapping I advise the following two: 1. Mind Manager (imo, the best one) and 2. Free Mind (well, that one is free)


Also available in russian.

Screenshoting. Weapons of choice

Most testers on everyday basis create defect reports, or bug reports or just submit bugs – you can name it as you wish. I’ve already shared my opinion regarding the importance of writing a good bug report. There I mentioned attachments as one of the three most important parts of a report. So, this is the part where screen content capture tools come to the stage. Let’s talk about them.

The niche of screen content capture tools is really large nowadays (you can check for yourself e.g. here or here or anywhere on the Internet) – well, it’s not only testers who use this software.
I’ve tried some tools and made my decision. So here they are – my “weapons of choice”: 1. SnagIt and 2. Win7 Snipping Tool

1. SnagIt

SnagIt – is a rather powerful tool that allows not only to make a screenshot fast and easy but to also add tons of different stuff to it, like borders, text with shadows and other effects, arrows, stamps and such. This makes it really convenient to emphasize the target screenshot spots and create kind of explanation schemas. SnagIt has lots of preferences and settings, e.g. 10+ profiles for capturing different content types (region, full screen, scrolloing window, menu with time delay, video…) thus it is a great aid when you need to make a very precise and detailed screenshot. As I’ve already mentioned there is a possibility to record video, which “weights” almost nothing after you archive it, which is really nice.
Besides all that great stuff that I’ve named, SnagIt has pretty good exporting capabilities – e.g. exporting to Word, Excel, PowerPoint, IM and sending via email or FTP

To cut a long story short, I can say that it’s an ideal tool for creating precise and beautiful screenshots for your needs.

2. Snipping Tool

Snipping tool – is a built-in screen capture tool in Windows 7. It is a good example of minimal art in designing software to solve a particular task (in our case - screenshoting). Within Snipping Tool you will not find dozens of settings and tweaks, but you’ll see a set of options capable to create a good screenshot fast. There are 4 basic capturing profiles (free-form, rectangle, window and screen) which actually covers most of cases. Here we have only two tools – pen and highlighter and this is not enough in half of cases. There is no export, but you can still send the created file using email.
To sum it up, Snipping Tool – is a pretty nice tool for simple screenshoting.

To put it in a nutshell: for creation of “heavy” and complex screenshots – use SnagIt, and when you need to attach just a simple screenshot - Snipping Tool will do.

Also available in russian.