-
Type:
Technical Task
-
Status: Closed
-
Priority:
Minor
-
Resolution: Completed
-
Affects Version/s: None
-
Fix Version/s: None
-
Component/s: App Builder, Workflow
-
Labels:None
Drafting TCs...
# | Test Scenario |
---|---|
1 | Workflow App can be created through the "New App" button |
2 | Workflow App can be created through the "plus" button |
3 | User can define/edit the name of a Workflow App that is being created |
4 | User can choose between "Simple" and "Workflow" App |
5 | User can cancel the creation of a Workflow App |
6 | Validate tooltip for the "Main Data Object" |
7 | Validate empty state when no object is selected |
8 | The list of Objects should inform the type of object (native or custom) |
9 | User can search for a Data Object |
10 | Validate empty state when there is no Data Object available |
11 | Results from Data Object search are on the fly |
12 | Validate no results state for Data Object |
13 | User can search for a Form View |
14 | Validate empty state when there is no Form View available |
15 | Results from Form View search are on the fly |
16 | Validate no results state for Form View |
17 | User can search for a Table View |
18 | Validate empty state when there is no Table View available |
19 | Results from Table View search are on the fly |
20 | Validate no results state for Table View |
21 | User is not allowed to deploy a Workflow App without a Name, Main Data Object, Form View, Table View or Deployment Type selected |
22 | User can deploy Workflow App as Widget |
23 | User can deploy Workflow App as Standalone |
24 | User can deploy Workflow App as Product/Site Menu |
25 | Workflow App deployed as Standalone can be opened through the successfully deployed message |
26 | User can define the translation of the name of a Workflow App and it will be displayed correctly in that language |