FAQ
- Valeriia Savinova
- Anna Iustus
- Mariia (Unlicensed)
How to update the back-end version manually
Abort the currently running process is terminal (Ctrl + C)
docker-compose stop
docker-compose rm -f
docker system prune -aRun curl again (look for up-to-date link here: https://github.com/jdi-testing/jdi-qasp-ml)
What is the Prediction Accuracy?
The Prediction Accuracy is displayed in the tooltip of each locator on the page.
The indicator of Prediction Accuracy shows the algorithm recognition confidence of an element. For example, if you see that the label “button” was recognized with 50%, then you should check this element and its label.
How to update the version of the plugin?
To update version
Run in the terminal
npm run patchor manually change version in the following files:
package.json
package-lock.json
manifest.json
2. Commit and push changes.
When your request has been merged, github actions will create a draft of the release with the current package.json version tag.
Branching
develop - base develop branch
issue_<YOUR_ISSUE_NUMBER> - feature and fix branch, started from master and merged into master when feature is ready
release_<RELEASE_NUMBER> - release branch, start from master
hotfix_<ISSUE_NUMBER> - fix for production version of application, start from master branch and merged into it master bugfix_<ISSUE_NUMBER> - fix for release, start from release branch and merged into it release, master
When the master branch is updated, all branches that are open at that moment (feature, fix) need to be updated.
Builds are sent to QA only after they have been merged into the master branch and the application version has been incremented.
CI/CD
The delivery pack is built automatically on commit in master.
Version compatibility list