ljmotta opened a new issue, #3903:
URL: https://github.com/apache/incubator-kie-tools/issues/3903

   This epic collects the action plan defined on the [strategy for implementing 
the E2E test suite for the new SceSim 
Editor](https://github.com/apache/incubator-kie-issues/issues/871).
   
   ## Phases
   1. https://github.com/apache/incubator-kie-issues/issues/950
   2. https://github.com/apache/incubator-kie-tools/issues/3902
   3. https://github.com/apache/incubator-kie-tools/issues/3901
   
   ## Test cases
   
   During the phases, we have to create tests to cover functionalities and 
non-functionalities of the new SceSim editor, and here we collect the scenarios 
to be covered on the test suite:
   
   ### Functionalities
   List of functionalities currently implemented in the SceSim Editor that are 
ready for testing:
   - **Functionalities**
     - Cheat sheet panel (just shows static content, worth testing with 
screenshot to make sure it renders properly?)
     - Copy as XML (confirm that changes in e.g. values/resizing are reflected 
in the copied xml)
     - Download as XML (confirm that changes in e.g. values/resizing are 
reflected in the downloaded xml)
     - Table operations
       - Resizing
       - Plus sign to add new row/column
       - Auto Resizing
       - Populating (confirm value is persisted)
       - Context Menus
         - **Scenario**
           - Insert Above
           - Insert Below
           - Insert multiple rows (above and below) (_currently not 
implemented_)
           - Delete
           - Duplicate
         - **Field**
           - Insert left
           - Insert Right
           - Insert multiple (left and right) (_currently not implemented_)
           - Delete
         - **Instance**
           - Insert left
           - Insert Right
           - Insert multiple (left and right) (_currently not implemented_)
           - Delete
         - **Selection**
           - Copy
           - Cut
           - Paste
           - Reset
       - **Restrictions**
         - There must always be at least one given and expect column in the 
Test Scenario table, and always one Given column in background table
         - Right clicking on Given/Expect/Scenario Description/# Cells should 
do nothing (_currently not implemented_)
     - Clipboard
     - Settings panel (_still under development_)
       - Rule
         - KIE Session (confirm value is persisted)
         - AgendaGroup/RuleFlowGroup (confirm value is persisted)
         - Stateless Session (confirm value is persisted)
         - Skip this test scenario during the test (confirm value is persisted)
       - Decision
   - Keyboard Shortcuts
   
   
   
   
   
   
   
   
   ### Non functionalities
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to