vothaison
commented
1 year ago Hi @brogreenmoon Here is a proposed rules for the validations of the steps. Given that currently each step has 3 peices of info: Page, Element, and Data.
- Action Clear: Requires Page and Element
- Action Click: Requires Page and Element
- Action Click Popup: Requires Page and Element
- Action Close Popup: None
- Action Delay: Requires Data - the miliseconds to delay
- Action Go to Url: Requires Data - the URL
- Action Input: Requires Page and Element
- Action Input by Code : Requires Page and Element (empty data means empty string)
- Action Run Code: (empty data means empty string) - the actual code to run
- Action Select Option: Requires Page and Element (empty data means empty string)
- Action Verify Attribute: Requires Page and Element and Data
- Action Verify Has Text: Requires Page and Element (empty data means empty string)
- Action Verify Has Value: Requires Page and Element (empty data means empty string)
- Action Verify IsEditable: Requires Page and Element
- Action Verify Is ReadOnly: Requires Page and Element
- Action Verify IsVisible: Requires Page and Element
- Action Verify Title: Requires (empty data means empty string)
- Action Verify Title Contains: Requires (empty data means empty string)
- Action Verify URL: Requires Data - The URL
brogreenmoon
quockhanh
Manage missing mandatory fields by showing an error at the codegen stage.
For example, I save a test case with missing actions, pages and elements, like so:
When the test cases are parsed it should check that mandatory fields are present, and if any are not present codegen should stop at the end of the "Parsing" phase with the message "Parsing FAILED." and not move onto "Cleaning folder".
Errors should be shown in the codegen log for these, e.g:
Error: testFailures.tcase - Line 1, Action "Click" is missing "Element" Error: testFailures.tcase - Line 2, Missing "Action" Error: testFailures.tcase - Line 3, Action "Input" is missing "Page" and "Element"