Page Comparison

...

You can start the Test Management via the Dashboard or by calling the transaction /DVD/KATE_TM.

...

_{Test Management, Test Cases tab}

It is good important to understand the differences difference between Test cases and Test plans. Test plan is basic organizational entity. Test plan allows combining you to combine different types and any number of test Test cases together. There are several specific actions that can be done on top of the Test Plan reminded further , mentioned in the text further. Definition of directories may seem similar to a Test plan definition but they have less/different options and are more folder like. Any Test Case cannot be executed without a Test Plan. Test plan serves as a frame for its test Test cases. Test plan holds further definition of execution, settings, testers, statuses, documents and otherothers. Test case carries basic information about the type (type of tested subject) and variants (particular details about tested objects).

...

One of the first steps while using Validate benefits is a Test case creation. 

There are 3 ways to create a new test Test case,:

• New test Test case button,
• Right-clicking at directory and selecting Add Test Case.
• Hotkey Shift + F1

...

The technical name for the test Test case (e.g. TST_CASE) has a Description field and a Directory field that can be selected to be pre-populated with the current directory, if . If it's not selected you can manually add the directory. Note: this field is mandatory and you cannot create test a Test case outside of the directory.

...

_{New Test Case window}

The Fields marked with a tick box checkbox are mandatory. 
The Test Case Type is a drop down menu, which contains the different types of Test Cases. Test Case Type 'Manual Test Case' is always preselected pre-selected by default.

Depending on your Validate setup, only certain Test Case Types may be visible. 
For example, if the Validate setup were to also contain contains BW Test Case Types, you will see an additional button at the bottom of the 'New Test Case window', where . Here you can define additional information, based on these Test Case Types. 

...

By pressing the Create new directory, (Shift + F2) a new directory is created and you can add subdirectories by right clicking on the in the context menu of an existing directory and choosing Add Subdirectory. 

...

Dir. Technical Name contains the technical name (e.g. FIELD_TST_DIR), whereas the Dir. Description is what is displayed in the navigation tree panel.
The Parent Directory field is pre-populated with the current directory, if . If this option is not selected the Parent directory needs to fill in be filled manually.

Delete directory and Test Cases

If Test Cases and/or directories are no longer necessary these can be deleted.

• By right clicking on In the context menu of an existing test Test case/directory and choosing delete.
• By Selecting Test Case/Directory and pressing the delete button, (Shift + F4)

_{Deleting items}

Transport Test Cases

Via the use of transports, Test Cases and their content can be transported from the one system to another system. Therefore you can define Test Cases in one system and then reuse the same test Test case in another system. If there already exists the same Test Cases or directories already exist, these will be overwritten when transported into the system.

...

...

Find and Find next

If you have many test Test cases and/or directories you can use the Find and Find next search features, to . To do so you can use the Find button or (Shift + F7).

...

If you want to check all Test Plans where a particular Test Case is used, use the "Where Used" feature found in the context menu displayed by right clicking on the of a Test case. The Result table contains all Test Plan information where this variant is used.

...

This part of the Test Management is dedicated to the test planning and test monitoring.

_{Test Management, Test Plans tab}

...

Mandatory fields are marked with a checkbox, the . The Dialog box now contains new button, Scope, and button Scope and allows you to edit the content of the Test Plan immediately. Test Cases can be also assigned/edited afterwards via the Edit command or by right clicking on in the context menu of the created plan and choosing Edit. 

...

...

This dialog window contains two main parts:

• Left part containing contains the tree of Existing test Test cases
• Right part containing contains your currently selected Test Plan tree

...

• Deleting Test Plan itself,
• Dragging items from Test Plan tree to Test Cases tree,
• Dragging parent onto its children,
• Dragging item outside of the plan,
• Dragging already incorporated test Test case / directory again
• Dragging or deleting variants of test Test case.

Except above mentioned, the items are fully moveablemovable. You can add new items / directories, change their order or parent, delete undesired items / directories, or select variants that are to be used in the testing. However, you are unable to create a new folder in the test Test plan or rename any of the items.

...

You can assign existing Test Plans to a specific person or to a list of people responsible for the testing. By clicking on the Assign testers icon or right clicking on in the context menu of the plan and choosing Assign testers (Shift + F2).

...

When setting the status of a Test Plan, it is necessary to have the status on Active so the testers can see this in their Worklist. 
Test Plans can have the following statuses:

• Active and Closed.

Test Cases can have the following statuses:

• Untested, In process, Failed, Successful.

...

Test Cases and Test Plans can have a Status Document, here you can add amore more detailed description of the testing results. To create a status document right , click on the context menu of a Test Case/Test Plan and select „Create Status Document" option.

...

Worklist view

In the worklist view, you can display all the Test Cases assigned to a given user , and are visible in their worklist. You can navigate via the worklist view button (Shift + F5).

...

_{Worklist window}

Simply enter the users user's SAP login and press confirm, if . If you want wish to reset the view, leave the User name field blank and press confirm.

...

You can filter the Test Cases by pressing Filter icon (Shift + F6). Test Cases or Test Plans can both be filtered by their Technical name, and . Test Cases can be filtered according to their status. It is also possible to use an  asterisk to broaden the filter.

...

Find and Find next

When you have many test Test cases and/or directories, use the Find and Find next are search by pressing the Find button (Shift + F7).

...

Test Plan Report

You can generate a documentation from the Test Plan in the form of MS Word document or HTML document. This report contains a list of all the Test Cases, including their statuses, Status Documents and additional information depending on the type of the Test Case.

...

Before actual generation, you can select Test Cases to be part of a Test Plan Report, type of generated document for Test Plan Report and what kind of information needs to be generated.

_{Test Plan Report Options}

...

You can schedule Test Plans to run on the regular basis and send notifications about the result.

Prerequisites

For Scheduling scheduling to take place, you need to start Scheduling Checker in the Test Management Settings.

...

The Scheduling Checker is reoccurring background job that checks for all the scheduled Test Plans every 15 minutes (i.e. if Scheduling Checker is executed on 17:40 it will check for Test Plans that are scheduled between 17:25 and 17:40).
You can set the Checking Period, which defines how often the Scheduling Checker checks for the scheduled Test Plans.
The actual precision of the scheduled time is dependent on this Checking Period – the smaller the number, better the precision. It is recommended to set a limit of up to 10 minutes. For a Checking Period of 10 minutes, the deviation is +10 minutes (so a Test Plan executed for 16:30 can be actually executed between 16:30 and 16:40).
You can also set the number of background jobs that are to be executed with in within a given Test Case.
Each run of the Scheduling Checker is logged and these logs are available from the Test Management Settings.

...

_{Overview of scheduled Test Plans (with filter enabled)}

How to Schedule a Test Plan

To schedule a given Test Plan, right-click on go to context menu of the Test Plan and select 'Schedule Test Plan'.

...

For each Test Plan you can defined the scope - select which Test Cases have to be executed in scheduled Test Plan.

...

Once the Test Plan has been scheduled and executed, you can check the logs by right-clicking on in the context menu of the Test Plan.

_{Show Scheduling Logs}

...

_{Scheduling Logs for given Test Plan}

If the email address is available and has been set, a notification about the results will be sent. 

...

When Scheduling Test Plans, it is useful to know the algorithm for the Scheduling Checker to better understand its behavior.
Scheduling Checker is scheduled as a background job every X minutes (X is a Checking Period in Test Management settings). During the Scheduling Checker execution, two actions are being performed:

...

You can create a historical snapshot of a Test Plan backend for Test Cases. This snapshot will save information about selected Test Plan and the actual execution status. To create the snapshot right click on go in the context menu of desired Test Plan and select 'Variants OveriewOverview' -> 'Create New Snapshot' option from the context menu. You can then select which Test Cases should be included in the snapshot.

...

It is possible to create snapshots automatically after each scheduled Test Plan execution by selecting 'Create Snapshot After Execution' option with in within scheduling options of a Test Plan. The Snapshot will be created only for Test Cases executed in scheduled execution.

...

To review historical snapshots that were created, right click on go in the context menu of desired Test Plan and select 'Variants Overview'->'Show Variants Overview' option from the context menu. A New screen will be displayed with the already created snapshots.

...

At the top of the screen you can select a period for which you want to display created snapshots as you can display multiple test Test plan history snapshots at once. By using F4 help you can change the date range and then by using of F8 refresh button, you will load the data of appropriate snapshots. The History overview screen contains 5 main tabs:

...

In this tab you can see one record for each Snapshot/Test Case pair. It contains information about the total number of variants present in the Test Case when snapshot was created, overall status of a Test Case, untested/successful/failed variant counts, and rows information.

...

In the 'User Comment' column you can provide any custom comment that will be saved there for later review.

Variant Overview Tab

Here is you will can see an overview of each Snapshot/Test Case/Variant combination. The information displayed includes the variant description, compare/reporting status, tested/error rows count and reporting status text if any.

...

This tab is only displayed , if any of the selected snapshots actually contain one or more ListCube Test Cases. For each Snapshot/Test Case/Variant combination you can see details of its variant settings and execution status of all steps.

...

This tab is only displayed , if any of the selected snapshots actually contain one or more Table Test Cases. For each Snapshot/Test Case/Variant combination you can see details of its variant settings and execution status of all steps.

...

Test Plan Replication to HP ALM

When the replication to HP ALM server is correctly setup in the Datavard Validate settings, you can replicate Datavard Validate Test Plans in the HP ALM server. To replicate a Test Plan, right click on it go in the context menu and select 'Others' -> 'Replicate to HP ALM'. To replicate multiple Test Plans, right click on , go in the context menu of a Test Plan Folder and select 'Replicate to HP ALM'.

_{Replicating Test Plans to HP ALM server}

Choose template from listbox the list box to fill a set of settings needed for the replication. For immediate customization of settings click on 'Edit' button. These changes will not affect any template. For the replication click on 'Continue' button. Last used template is saved for each replicated Test Plan and it will be preselected pre-selected during next replication.

_{Selecting template before replication of Test Plans to HP ALM server}

...

_{Worklist in Validate Dashboard}

This area with in within Validate is focused on the testers, and those who see their Test Cases/Test Plans that are assigned to them.

_Worklist

Test Plans with the status New are not displayed here, in order to make New test  Test plans visible, their status needs to be changed to Active. You can do this through the Test Management -> Test Plans tab. Users will only see their assigned Test Cases. Also directories are not displayed here.
To indicate which phase of testing the Test Cases are in, you can change their status. To change the status, click on the Set Status icon (Shift + F4), or right click on the test case, in go in the context menu of the Test case. In the following window where you can add a description for the Test Cases and set the status to Untested, In process, Failed or Successful.

...

In Test Plans tab, there is an option to execute all Test Cases in given Test Plan. For each Test Case Type, execution options are given and user can select which parts to execute and which do not (i.e. execute only Before Image for all ListCube Test Cases). 

...

After clicking on "Change Selection" button, the scope of Mass Execution can be defined. Functionality is supported for all Test Cases that can be selected (i.e. Manual Test Case type cannot be selected, because it does not support the Mass Execution option).

...

When backend Test Cases are selected for mass execution, you can define which test steps should be executed from each test Test case type. List of test steps depends on chosen backend scenarios. Please refer to chapter 8 for more details of about test steps for each type. Setting 'Number of jobs per Test Case' displayed on Figure 119 defines in how many background job jobs for each chosen step are to be executed. 
Each backend test Test case type contains the option 'Run Sequentially'. If this setting is set, all chosen test steps will be executed in the order in which they are defined within the list. Execution of a step will be started once the preceding step is finished. There is a maximum time setting that once it is reached, while waiting for the preceding step to finish, will end the execution of the test Test case. Refer Please refer to Settings chapter for more details. If 'Run Sequentially' option is not used, all selected test steps are executed in parallel each using the specified number of jobs. No wait is used for these cases. 

...