cyluxx / chrec Goto Github PK

Make whole document screenshots for better visual comparison results.

Display the current programm state in a statusbar located at the bottom of the GUI.

This includes:

• Recording status
• Replaying status
• Important settings, like setup Browsers

A user should be able to manually:

• add an Action to a Sequence
• edit the attributes of an Action
• delete an Action from a Sequence

Write a user manual

Refactor Core Model and test it properly.

The GUI should be easier to understand and to handle.

Use Computer Vision techniques to generate stable locators.

The current version of the preload script, which contains essential parts of the recorder code has to be reworked, in order to make it more consistent.

Add/Edit the following Actions:

• Clear
• Read
• Select
• Submit
• SwitchToContext
• SwitchToDefaultContext
• SwitchToParent
• Type (remove Key attribute)
• WaitForAddedNode
• WaitForRemovedNode
• WaitForNodeAttribute

Add functions to the native menubar.
For example:

• undo
• redo
• quickbar functions

Display the boundingbox of a recorded element graphically, inspired by Chrome devtools.

Make sure the Alex export is working properly and eliminate any unconsistencies.

Use Computer Vision techniques to generate stable locators.

A user should be able to manually:

• add a custom Locator to an Action
• edit the attributes of a custom Locator
• delete an custom Locator from a Sequence

Build a component with checkbox inputs for every locator generating method. The user can decide which methods will be used, while recording an Action.

Run autosave after choosen user interactions with the program.

Invent a system to make read Actions dependent on previous executed type Actions.

For Example: A username was typed and is now readable after a login of a given application.

Improve the current confusing test results GUI.

Possible solutions:

• tree list view for ProjectTestResult > SequenceTestResult > BrowserTestResult > ActionTestResult hierarchy

The current approach of highlighting the last recorded Element involves unnecessary complicated communication between webview content and core program. The current implementation is buggy and seems to behave inconsistently.

A better approach would be a later performed image manipulation on the recorded screenshot, based on the boundingbox coordinate.

A user should be able to manually:

• edit the attributes of a Sequence
• delete a Sequence from a Project

Add Product Name, Version, Description, Author etc. to corresponding meta files.

Add Logo

Use the BoundingBox of a given Element to generate a robust locator.

Currently, the Robula+ algorithm has to be built and included manually. In order to do so, license matters have to be clarified.

Use BoundingBox of other significant elements in order to transpose and find referenced original element.

Integrate Alex directly via its Rest API and provide the necessary configuration options.

Improve the look and feel by showing the user the current executed Sequence, Browser and Action. A progress bar could visualize this action.

The GUI should be easier to understand and to handle. Webview should maximize by default.

Generate (Java) Selenium code from recorded Sequences.

Add modals for different error/info cases:

• No Selenium Server / Grid connected
• First Action is not a GoTo Action
• Reset Settings confirmation
• Session not created: Old Webdriver version
• Internal Error with stacktrace
• Invalid ChRec Json