Step In/Step over execution. - Step In - executes one next command, so all commands on line are processed.- Step Over - executes all commands on current line, and go to next one.

Do some stuff in AUT then suspend.Then Q7 stop on breakpoint - it Unfreeze AUT, so it is possible to perform some actions. But be aware changes in AUT could cause test to fail.

Support for restart of test case during debug. - Restart is supported the same way as in Recording/Replay.

No focus issue then debug.Because of Q7 runtime architecture and ideas, there is no need to worry about focus/active windows on debug Since all ECL commands know about target control, so all operations are go to destination, but not your dev Eclipse instance.

Support for Test suites

Since 1.2 Q7 has build in support of grouping Test cases into Test suites.

Testsuite is a way to logically organize test cases. Each test case could be included into any set of test suites. Suites also could be included one into another.

To create test suite "New Testsuite" wizard could be used.

After suite is create we could add test case references to it.

Test cases could be executed the same way as test cases.

Testsuites are saved in portable format:

OS-independent keyboard shortcuts

One of the challenges in test case portability across platforms is difference in keystrokes. For example, on Mac OS X many shortcuts use Command instead of Control. The Eclipse platform has platform-independent way of representing modifier keys (see Eclipse help):

Modifier

Windows

Linux

Mac OS X

M1

Control

Control

Command

M2

Shift

Shift

Shift

M3

Alt

Alt

Option

M4

undefined

undefined

Control

Thus, despite the fact that Copy command is represented as ⌘C on Mac OS X and Ctrl+C on Windows and Linux, in Eclipse it is represented as M1+C on all platforms, and here's an example what we get in recorded script when using keyboard shortcuts:

This ECL code can be executed as is on any platform. However, there's one more place where keyboard shortcuts are not represented in platform-independent way – tooltips. Here's an example: When we record clicking on this button, we get a snippet like this:

Trying to reproduce it on Windows will cause the test fail, because there's no such button. Prior to Q7 version 1.2 the only way to make test portable was to use regular expressions for selecting, like this:

But since 1.2, we replace text representation of accelerator keys in tooltips: and produce code which can be replayed as is on any platform without modifications:

The disadvantage of this approach is that this change breaks existing test cases, but migration can be done quick and easy using global search-replace in Q7 and replacing Ctrl+ with M1+, Shift+ with M2+, and Alt+ with M3+: