Show HN: Datadog QA – TUI for Jira users to perform QA of future GitHub releases | Hacker News Reader

Show HN: Datadog QA – TUI for Jira users to perform QA of future GitHub releases

github.com

40 pointsofek10 comments

Hey there! We use this currently for releasing the Agent [1] and thought it would be nice to open up broadly for others.

[1]: https://docs.datadoghq.com/agent/

Open articleView on HN

It is awesome to see the increase in popularity of `rich` and `textual` libraries! Check them out if you want to develop a TUI application or just make sure your CLI app looks awesome. @willmcgugan is doing a great job! <3

Love to see the use of `httpx` as well, a great Python HTTP client with support for both sync and async APIs.

If I'm reading correctly this translates PRs into test tickets? Is that a workflow that a lot of teams use? We usually just flow the feature ticket from grooming to dev, to code review to QA, then release.

This workflow has historically worked for us quite well. We merge in features rapidly so having GitHub be the source of truth for activity that needs to be tested is beneficial for never accidentally missing items.

FYI we used to use Trello (using the same workflow) but switched to Jira and wrote this tool in the process. Jira aggregation in the web app can be quite slow so actually this tool makes tracking a bit nicer as well.

FYI: Installation is `pipx install ddqa` and then on first run it should ask you for userIDs and account tokens.

What is "test candidates" and how are they detected from a diff between two commits?

A candidate is a commit between 2 Git references https://datadoghq.dev/ddqa/actions/create/

Do I need to be a datadog user for this, or just a Jira/Github user?

Just a Jira/GitHub user, as we are

How does Agent refer to ddqa repository which was linked in the title?

We install the tool and run the documented actions for the Agent repo. Example command: https://datadoghq.dev/ddqa/actions/status/

Reply on news.ycombinator.com