Testing

The following scenarios to open the transition screen available:

  1. My Dashboard > My Applications > Choose the project > Actions column > Process option;
  2. Project menu > Dashboards > Overview > Your assignments module > Choose the application > Actions column > Process option;
  3. Project menu > Dashboards > Portfolio > Actions column > Process option;
  4. Project menu > Import > Start import > Classic import / Import from CSV file / SCCM Import /Catalogue & UM Import > Application upload session > Finish

Apptimized shows the following screen when successful:

testing_01.PNG

The testing process starts by clicking on the Skip to [Step name] button (before or after discovery step) and clicking in the Testing module on the Transition screen. An imported application into a project is a prerequisite. 

testing_02.PNG

Two testing scenarios available in Apptimized portal:

  • Testing – Self Service;
  • Testing – Factory Service.

Note. A source for Testing step downloads at the Import step (see Classic import, CSV import, SCCM import, Catalogue & UM Import). Depending on the project workflow structure, a source can be an EXE file, a package).
Next, the most common cases with the Testing are provided:
1. The project workflow consists of 3 steps (Discovery - Self Service, Packaging - Factory Service, Testing - Self Service). A user uses a Classic import option to import the source (EXE file). The user goes through the steps sequentially. When the package is ready the user starts the Testing step with the package (i.e., Selects the testing platform > Starts VM > Opens Packages folder >Launches install.cmd file > Performs the testing actions > Finish VM > Reviews the testing results).
2. The project workflow consists of 3 steps (Discovery - Self Service, Packaging - Factory Service, Testing - Self Service). A user uses a Classic import option to import the source (EXE file). The user skips the Discovery - Self Service and Packaging - Factory Service steps. The user starts the Testing step with the existing source (i.e., Selects the testing platform > Starts VM > Opens Source folder >Launches EXE file > Performs the testing actions > Finish VM > Reviews the testing results).
3. The project workflow consists of 1 step (Testing - Self Service). A user uses a Classic import option to import the source (MSI file). The user starts the Testing step with the existing source (i.e., Selects the testing platform > Starts VM > Opens Source folder >Launches package file > Performs the testing actions > Finish VM > Reviews the testing results).

Testing – Self Service

A user can record a guide to install and configure the application on Apptimized VMs. Also, a customer can enable a testing option and set the status of testing.

Testing - Self Service characteristics:

  • A user tests created packages on his own.
  • A user runs and documents test cases.
  • A user logs installation or functional errors.
  • A user provides debugging guidance.

The Testing - Self Service option is available under the Testing - Self Service module in the Transition screen.

testing_03.PNG

Apptimized shows the following screen when successful:

testing_04.PNG

A field "Select testing – self service platform" is filled automatically and can be changed if needed. To change the testing – self service platform, click the drop-down menu as it is shown in the screenshot below:

testing_05.png

The option to revert to the transition screen is available under the Go to Transition screen button.

Testing – Self Service process

The option to start the testing – self service process is available under the Start VM button.

Apptimized shows the following screen when successful:

testing_06_2.png

The file synchronization process may take few moments. Apptimized shows the following notification:

testing_06_3.png

Note. There is often a situation when a user has already run 2 VMs in parallel. To continue planned activities within the current workflow step, a user must terminate an irrelevant VM. In this case, Apptimized shows the warning box with a list of VMs which are currently running by the user:
listvm_01.png
The information is grouped into the following categories in the modal window: 
1. Application
2. VM started time
3. Workflow progress
4. Link
The option to select a VM for termination is available under the Go to VM link. A new tab opens when successful:
listvm_03_testing.png
When a VM is terminated, a user returns to the screen where he needs to restart a VM (previously a user started a VM but received a modal window with a list of running VMs).

When the synchronization process is finished, Apptimized shows the following screen:

testing_07.png

Note. If the internal error while starting VM occurred, Apptimized shows the following screen:
testing_error-massage_02.png
The following actions are recommended for consideration by a user:
1. Contact the Apptimized support
2. Go to image page button > Select discovery – self-service platform field > Start VM button
testing_error-massage_01.png

The uploaded files locate in the Apptimized files folder on the VM desktop.

To start the installation process, a user opens the .EXE file located in the Source folder.

testing_08.png

Every action is captured as a screenshot which is shown in green boxes appearing on the right-hand side:

testing_08_1.png

When application installation is completed, a user can provide further configurations (only the Edit and Settings categories).

The options to finish the VM session is available under the Finish button.

testing_10.png

The following interface will appear when recording session with Apptimized VM finishes:

testing_13.png

The option to restart the VM testing session is available under the Restart button. To confirm the restarting the VM Apptimized shows the following modal window:

testing_12.png

VM control menu

The VM control menu panel is available in the upper right corner of the VM interface.

testing_01.png

Next, each settings category is shown in more detail.

testing_02.png

Table 1. VM control menu

 

Control menu category

Details

1

Screenshots

This setting indicates the screenshot mode.

On and Off options available.

The default value is On.

2

RDP

This setting enables a user to work on the VM directly via RDP rather than a browser window.

discovery_16.png

The option to download a file is available under the Download RDP file.

The RDP file is available in the Downloads folder in user’s PC.

discovery_16_10.png

When the remote connection is set, copy the RDP password paste to the modal window. The remote desktop connection window appears when successful:

discovery_16_11.png

3

VM Snapshots

The setting enables to create a snapshot of the VM to save its current state or to revert to a state saved earlier.

This is applicable when the application has prerequisites that need to be present before a certain action (i.e., Discovery, Packaging, or Testing) can be started.

discovery_17.png

The snapshot option is available under the VM snapshot button > Snapshot name field > Take button.

4

Clipboard

This setting enables a user to put text from the user’s system to the VM clipboard. Transferring clipboard content between the host machine and the VM is performed via "Cut & Paste" in most user scenarios. If the user experiences any issues with "Cut & Paste", the Clipboard button can be used to put the text to the VM's clipboard.

discovery_18.png

5

Fullscreen

This setting enables to put a browser in a full-screen mode.

6

Restart

This setting enables a user to redo the testing session on a restarted VM.

The following restart options available:

  • OS (Operating system restart. Equal to Power > Restart);
  • VM (Equal to the Reset button on the real PC);
  • Session (Restart current session. All unsaved progress will be lost).

discovery_19.png

When the restart option is chosen, the confirmation model window appears.

7

Finish

This setting finishes the VM when the testing session is completed.

Testing – Self Service screenshots

The option to edit the screenshots is available under the Continue with Testing – Self Service screenshots button.

testing_14.png

Apptimized shows the following screen when successful:

testing_16.png

The following options to log test session results are available:

  • Untested;
  • Success;
  • Failed.

testing_17_1.png

The default value is Untested.

The field Optional comment can stay blank.

testing_17_2.png

Screenshots can be excluded from testing by clicking the Delete button.

testing_19.png

Screenshots can be excluded from testing in a multiple mode by unticking checkboxes in front of their ID and clicking the Delete selected screenshots button.

testing_18.png

Apptimized shows the following modal window:

testing_20.png

When clicking on the Confirm button, Apptimized shows the notification:

testing_21.png

Screenshots sequence can be changed in testing by clicking the Up or Down buttons.

testing_22.png

testing_23.png

Comments to the screenshots can be edited by clicking on the comment cell.

testing_24.png

The Additional comment (Optional) field can stay blank.

testing_25.png

If any problems occur, the option to contact support is available under the Did you run into problems? button.

testing_26.png

Apptimized shows the following modal window:

testing_27.png

When the Contact support option is chosen, the live chat with the support team appears:

testing_28.png

When the Log problem option is chosen, the modal window appears:

testing_29.png

The problem category can be chosen by ticking checkboxes in front of their names.

Screenshots editing mode finalizes when clicking the Save changes button.

Apptimized shows the following interface when successful:

testing_30.png

The generated document is available in PDF and HTML formats. To download a document, click the Download generated HTML document or Download generated PDF document buttons.

The option to edit a testing document is available under the Edit generated document button. The document editing finalizes by clicking the Save button.

testing_31.png

The option to return to the testing self-service screen mode is available under the Revert to Testing – Self Service Self Service button.

The option to finish the testing process is available under the Finish button.

Apptimized shows the following screen:

testing_32.png

Testing – Factory Service

Testing – Factory Service characteristics:

  • Apptimized tests created packages for a user.
  • Apptimized runs and documents test cases based on user’s requirements.
  • Apptimized logs installation or functional errors.
  • Apptimized debugging guidance.

The Testing - Factory Service option is available under the Testing - Factory Service module in the Transition screen.

testing_33.png

Apptimized shows the following screen when successful:

testing_34.png

All required fields are marked with an asterisk *.

The option to provide a comment is available under the Reference field.

The option to choose the discovery platform is available under the Testing platform field.

testing_35.png

Two priority options are available: Normal and Urgent. The default value is Normal.

The option to submit the testing request is available the Submit request button.

Apptimized shows the following modal window:

testing_36.png

The option to change the Normal priority to Urgent before approving the request is available under the Need it sooner? Upgrade to Urgent by clicking here button.

The option to create the request is available under the OK button.

Apptimized shows the following screen when successful:

testing_37.png

This is an initial screen, and all blocks except the Status block are empty.

This screen provides information on the Apptimized Testing – Factory Service request (i.e., request progress and status). Additional information that might be needed during the testing process will be exchanged here.

Next, each Testing – Factory Service block is shown in more detail.

Status block

The Status block shows testing progress. The following request statuses appear depending on the Testing – Factory Service progress:

Table 2. Testing request statuses

Request status

Description

Incoming check

The request has not been processed by the Apptimized team yet. The request is in the queue.

In progress

The request was processed by the Apptimized team. The request is in progress.

Action required

The Apptimized team asked the user a question. The user answer is needed.

Delivered

Testing results are available to the user.

Testing results can be provided in PDF and HTML formats.

Error analysis

The user rejected the Testing results. Apptimized team fixes bugs in the Testing document.

Approved

The user has confirmed the Testing results.

Canceled

The user canceled the Testing request at the processing stage.

The option to cancel the request is available under the Cancel Request button.

testing_38.png

testing_39.png

Apptimized shows the following modal window to confirm the request cancellation:

testing_40.png

Apptimized shows the following modal window when successful:

testing_41.png

A user can cancel the discovery request until the Delivered status is achieved, and the discovery deliverables are available.

testing_42.png

If a user is not satisfied with the testing results, they can be rejected in the Deliverables block.

When a user is satisfied with the testing results, they must be approved in the Status block. The option to approve the request is available under the Approve Request button. The Approve Request button becomes active when the Delivered status is achieved, and the testing deliverables are available.

Apptimized shows the following modal window to confirm the request approval:

testing_43.png

Apptimized shows the following screen window when successful:

testing_44.png

Note. When a user approves the request, the option can`t be canceled.

Deliverables block

This block provides the testing results to a user. Discovery results can be provided in PDF and HTML formats.

The option to download the testing results is available under the Download button.

testing_45.png

If a user is not satisfied with the testing results, they can be rejected to further processing by the Apptimized team. The option to reject the testing results is available under the Reject button.

testing_46.png

Comments & attachments block

The option to provide comments or attachments to the Apptimized team is available under the Comments & attachments block.

testing_47.png

The option to add supplementary attachments (i.e., screenshots, additional file) is available under the Select file button (Choose a file > Open button > Add button). The file must be a maximum of 10 MB.

testing_48.png

Apptimized shows the message history interface when successful:

testing_49.png

Finish Testing - Factory Service

The Finish button becomes active when a request is approved by a user.

testing_50.png

The option to create a new request is available under the Create new request button. Apptimized shows the following modal window to confirm the request approval:

testing_51.png

Apptimized shows the following screen when successful:

testing_52.png

The option to finish Testing- Factory Service process is available under the Finish button.

testing_53.png

Apptimized shows the following screen when successful:

testing_54.png