Page History
Section | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
...
Panel | |||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||||||
|
Release highlights
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
...
And more...
Document Generator
- XRAY-6659: Xray Test Repository - Make the "Doc Gen" option available in the "All" and "Orphans" views
- XRAY-6623: When disabling the Document Generator, the option in Xray Settings should disappear too
- XRAY-7022: Add the possibility of defining if tests from a sub-folder must be exported using Doc. Generator on Test Plan board
- XRAY-7019: Add the possibility of defining if tests from a sub-folder must be exported using Doc. Generator on Test Repository board
- XRAY-7193: As a Jira admin, I should be able to enable/disable Doc Gen at the project level
- XRAY-7618: As a user, I should be able to use Doc Gen on Agile Boards
- XRAY-7024: Provide a mapping to print the folder name which the test belongs to when the test is being exported from the Test Plan or Test Repository boardXRAYCLOUD-2705: Users must be able to search for archived test runs by status
Just one more, yet important, thing...
...
- Tutorials with automation tools & frameworks
- Integration with Travis CI
- Integration with Ranorex
- Integration with GitHub
- Testing web applications using Playwright
- Testing using Cypress and Cucumber in JavaScript
- Testing Node.js apps using Cucumber.js in JavaScript
- Testing web applications using Mocha and WebdriverIO
- Testing using WebDriverIO and Cucumber in JavaScript
- TTT: Model-Based Testing
- TTT: API Testing
- Integration with other Jira apps
- Integration with Automation for Jira (added examples for implementing automation rules in different ecosystems and CI/CD tools, including Azure DevOps, Travis CI, etc)
- Integrations from the community
- Integrations from the community and other products (included a GitHub Action to interact with Xray, from within GitHub)
...