Test Report

Testi ng Status by Category

21
Total Result 2
19

12
Workbench Integration 1
11

1
Performance
1

1
Logging 1

3
Error Handling
3

4
Count - Test Name Status
Coding Standards
Test Category Pass 4 (empty) Total Result
Coding Standards 4 4
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22
Error Handling 3 3
Logging 1 1
Performance 1 1
Workbench Integration 11 1 12
Total Result 19 2 21
Test Number

UT-0001

UT-0002

UT-0003

UT-0004

UT-0005

UT-0006

UT-0007

UT-0008

UT-0009

UT-0010

UT-0011
UT-0012
UT-0013
UT-0014
UT-0015
UT-0016
UT-0017
UT-0018
UT-0019
UT-0020
UT-0021
 Test Name

Variable Naming Conventions

Function Naming Conventions

Function Description

Inline Comments

System Exception Handling

User Defined Exception Handling

Unhandled Exception

Execution Logging

Module Registration

Workbench Execution

Performance
Visualization configuration
Disable Run Button
Enable Stop Button on receiving Execution ID
Stop Button Ouput is got for all 3 cases :
a) The docker is still not running the process
b) The docker is running the process.
c) The docker has almost finished running the proc.
If the execution Fails due to a module error, the button is reset to Run.
After successfully stopping the process, the Stop button is replaced with the Run button.
Message returned from the Stop Execution API is projected onto Redis and the Node Log is saved by updating the node.
 Test Description

Ensure that code is following variable naming standards

Ensure that code is following function naming standards

Ensure that each function's purpose is well articulated

Ensure that logic flow of the code is well documented

Ensure that system defined exceptions are trapped and reported (where applicable)

Ensure that any user defined exceptions are trapped and reported (where applicable)

Ensure that there are no paths in the logic that will make the code fail behind the scenes without letting the user know about
status. For example, when a negative number is passed to an argument which theoritcally only accepts positive values

Ensure that each code logs its execution details in a persistent manner

Ensure that any module code is correctly registered in workbench configuration database with all required information being c

Ensure that any module, workflow or toolbox that is added to workbench executes succesfully when invoked directly from wo

Ensure that any new module runs on the benchmark dataset within the standard SLA on the test-bed configuration
Ensure that any new module is providing the outputs in the correct format as per chart requirements
Disable Run button till we get an Execution Id which can be used to kill the process.
Enable Stop Button on receiving Execution ID

a) The docker is still not running the process

b) The docker is running the process.
c) The docker has almost finished running the proc.
If the Run Fails, the button is reset to Run.
After successfully stopping the process, the Stop button is replaced with the Run button.
Message returned from the Stop Execution API is projected onto Redis and the Node Log is saved by updating the node.
 Expected Result Test Category Test Date

Variable names follow the project coding

standards Coding Standards 25-Feb-2020
Function names follow the project coding
standards Coding Standards 25-Feb-2020
Detailed description is included in the code for
each function Coding Standards 25-Feb-2020

Comments are available throughout the code

explaining each logical functionality and the
comments are easy to follow Coding Standards 25-Feb-2020

System exceptions are trapped and handled in

the code Error Handling 25-Feb-2020

User defined and function specific exceptions

are handled in the code Error Handling 25-Feb-2020

There are no unhandled exceptions in the code Error Handling 25-Feb-2020

Every call to the code saves an execution trail

(log) Logging 25-Feb-2020

Module's metadata is captured fully and

without any errors Workbench Integration 25-Feb-2020

Module/Workflow/Toolbox executes when run

from workbench Workbench Integration 25-Feb-2020

Performance is code is found to be satisfactory Performance 25-Feb-2020

Module outputs can be visualized correctly Workbench Integration 25-Feb-2020
Run Button is disabled till Execution ID is receiveWorkbench Integration 25-Feb-2020
Stop Button is enabled once the Execution ID is Workbench Integration 25-Feb-2020
Workbench Integration 25-Feb-2020
The execution is stopped successfully. Workbench Integration 25-Feb-2020
The execution is stopped successfully. Workbench Integration 25-Feb-2020
The execution is stopped successfully. Workbench Integration 25-Feb-2020
Button resets to Run button. Workbench Integration 25-Feb-2020
Button resets to Run button. Workbench Integration 25-Feb-2020
Redis Log displays the message with a Failure icoWorkbench Integration 25-Feb-2020
Iteration # Actual Result Status Screenshot No

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected

1 Same as expected

1 Same as expected Pass

1 Same as expected Pass

1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
1 Same as expected Pass
Sl No Screenshot
1

4
5

8
9
Coding Standards Pass

Functionality Fail
Error Handling NA
Logging
Workbench Integration
Performance
Field Name
Test Number

Test Name
Test Description
Expected Result
Test Category
Test Date

Iteration #

Actual Result
Status
Screenshot No
Description
Unique number for each distinct test. For example for unit testing a tst number will
be of the form "UT-XXXX"
Name identifying the test
Detailed description of the purpose and scope of the test
Elaboration of what is the expected behaviour when the test is executed
Field identifying one of the many different categories of testing
Date of Testing in DD-MMM-YYYY format
When a test is run multiple times, this field helps identifies the actual iteration
number
Details of the outcome from the test
Pass/Fail. Use NA if test is not applicable
A reference to the Defect screenshots
Test ID
1
2
3
3
3
3
4
5
6
Test Name
Disable Run Button
Enable Stop Button on receiving Execution ID
Stop Button Ouput is got for all 3 cases :
a) The docker is still not running the process
b) The docker is running the process.
c) The docker has almost finished running the proc.
If the execution Fails due to a module error, the button is reset to Run.
After successfully stopping the process, the Stop button is replaced with the Run button.
Message returned from the Stop Execution API is projected onto Redis and the Node Log is saved by updating the node.
Test Description
Disable Run button till we get an Execution Id which can be used to kill the process.
Enable Stop Button on receiving Execution ID

a) The docker is still not running the process

b) The docker is running the process.
c) The docker has almost finished running the proc.
If the Run Fails, the button is reset to Run.
After successfully stopping the process, the Stop button is replaced with the Run button.
Message returned from the Stop Execution API is projected onto Redis and the Node Log is saved by updating the node.
Expected Result
Run Button is disabled till Execution ID is received in the UI.
Stop Button is enabled once the Execution ID is received.

The execution is stopped successfully.

The execution is stopped successfully.
The execution is stopped successfully.
Button resets to Run button.
Button resets to Run button.
Redis Log displays the message with a Failure icon against it.