Screenshots taken during “Steps Capture” cannot be edited during the capture

The "Steps Capture" capability is a new feature of Sprinter 11.5 that enables users to create test steps by capturing user actions in the application under test (AUT). This feature allows the user to add screenshots to the test steps that can be taken during the capture process.

The screenshots can be opened during the capture process by clicking on the camera icon next to each step containing a screenshot. The user may want to edit them to suit his needs for example cropping parts of them. However these screen captures modifications are not saved when done directly during the "Steps Capture" process.

To reproduce the problem:

· Open Sprinter and in the "Plan" tab select to create a new test.

· Click the <Steps Capture> button and record any user action against the AUT.

· Click the camera icon to take a screenshot of the AUT.

· Click the image icon next to the recorded step to open it.

· Make any modification to the image and save it.

· Click again the image icon next to the recorded step to reopen it, the modified image will be displayed.

· Stop the steps capture by pressing the <Stop> button.

· Open the image saved with the test, the original image will be displayed with the changes discarded.

This is the behavior by design, the screenshots should not be modified with an external software.

It is possible to work around the issue by modifying the images once that the "Steps Capture" session is over, from Sprinter "Plan" tab. In this case, the modifications will successfully be saved.

How to enable/disable technology Add-ins/support in Sprinter

New entry/item on "Application" list

1. If Power Mode is "Off", set to "On"

2. Under the "Power Mode" section (lower left section), select/highlight "Application"

3. Methods:

o Automatic:

1. Click "Quick Add"

2. Select item representing application under testing

3. Click "Ok"

Note: This attempts enabling add-ins/technologies according to application type

o Manual:

1. Click "Add"

2. Input a Name

3. Select application type (Web Application or Desktop application)

4. Enable desired items under Technologies header.

5. (Optional) Enable "Start the application when the run begins"

6. Click "Ok"

Current entry/item on "Application" list

1. If Power Mode is "Off", set to "On"

2. Under the "Power Mode" section (lower left section), select/highlight "Application"

3. (Optional) Change to item under "Application" dropdown list on right upper side where setting would be changed

4. Click "Edit" button (2nd from left to right) on upper middle of script.

5. Under "Technologies" section, enable/check/activate or disable/uncheck/clear/deactivate checkbox of desired technologies/add-ins

6. Click "Ok" on lower right corner to save changes

Software Prerequisites for installing Sprinter 11.5

Software Prerequisites

The following are the prerequisites your system requires before installing Sprinter. If you run the Sprinter installation program and are missing these prerequisites, the installation program prompts you to install them.

  • Windows Installer 3.1
  • Microsoft Data Access Components 2.8 SP1
  • Microsoft Visual C++ 2005 SP1 Redistributable Package ATL Security Update
  • Microsoft Visual C++ 2010 Service Pack 1 Redistributable Package MFC Security Update
  • Microsoft .NET Framework 3.5 with SP1
  • Microsoft .NET Framework 4.0. This requires an internet connection when installing from an msi installation. If unavailable, contact Microsoft for the installation package to manually install.

New features in Sprinter 11.50

HP Sprinter 11.50 contains the following new features:

  • Manual Test Authoring – A Plan mode allows the creating and editing of ALM/QC manual tests. This new functionality allows users to save time when authoring manual tests.
  • Scanners – Sprinter can automatically detect defects during a test run using its built-in scanners: Spelling, L10N, Web Compliance, and Broken Links. A Scanners API allows users to create custom scanners.
  • Exploratory Testing Enhancements – Exploratory testing enhancements allow the creation of formal tests from informal exploratory test runs.
  • Storyboard Export – The storyboard, which shows user actions and screen shots, can be exported to a report in Word or PDF format.