qlane works with GitLab
about 1 month ago
Merge requests on GitLab get the same testing as pull requests on GitHub, plus one comment per defect and a timeline for every recording.
Connect GitLab, register your repositories, and qlane tests merge requests the way it tests pull requests on GitHub: it runs the cases, posts the results on the merge request, and answers when you mention it in a comment.
Comments got quieter on both platforms. Each defect now has a single comment that qlane edits as the change evolves, instead of a fresh batch of comments on every push.
@qlane test checkout with a saved card
4 cases passed
Saved card, new card, 3-D Secure, refund
- GitLab support: connect GitLab, register repositories, test merge requests, and mention qlane in merge-request comments.
- One comment per defect, edited in place as the change evolves.
- Network requests, console output and the agent's actions sit on the same timeline as the session recording.
- A bug's timecode jumps the recording to that moment.
- Sandbox pages for the project and the organization show what is running, with details in a side panel.
- When a setup goal fails, the reason is shown, and you can report it or run it again.
- Test credentials can carry facts and notes for the agent.
- Dashboard, Overview and Coverage Matrix are marked Beta.