Product Roadmap Q2-2020
- Migrate advance view from JSON representation to command representation
- An advanced command editor (IDE) that provides users the ability to modify and maintain their test cases by typing commands. This IDE will provide autocomplete, and syntax highlighting
- Project Management: Existing folders and all their dependencies (test cases and artifacts) can be associated with a project. Further, users can switch between projects and see only related assets (i.e. test cases and artifacts). Control mechanisms to allow access to users would be available for administrators. Users can be assigned to multiple projects
- Organizational Enhancements: Folders for function, Test case sections coloring, command indentations/marks for conditional and looping structures, and allow folders within execution set test case
Lanny,
The long term plan is to provide a full editor with IDE capabilities. I will post a video here to give you some ideas. We will keep the JSON editor around in case users are using it. However, with the new editor as well as the new versioning capabilities, we feel strongly that users will abandon the JSON editor.
I would appreciate if you let us know if you are using the JSON editor in any form, and how this could potentially impact your project.
--Rex
Rex,
Thanks again for your quick response!
We are designing an internal tool for automation developers. Because our test cases steps are standardized and well formatted, we are trying to automatically map our manual test cases to S7 scripts. So the advanced editor would be the interface to import machine created test scripts. Current standard and format of either Json or Command Editor will work. But the only thing we are worrying is our tool will be broken if advanced view editor changes its standard or format.
Please sign in to leave a comment.