Datadog QA
Dev tools
release testing tui
SHOW HN2023
40points
10comments
#1,217of 3,109 in 2023
Top 40%of 2023 by points
How HN took it
CuriousMostly questions and neutral comments
0 positive, 5 neutral or asking, 0 mixed, 0 critical, out of 5 comments about the project. Thread score 0.00.
The thread, comment by comment
Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.
positive neutral or mixed critical about another commenter or something else the maker
What HN said
What people liked
Useful GitHub-as-source-of-truth workflow for not missing test items
From 1 comment
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…
ofek on HN
Tool makes Jira tracking nicer than slow Jira aggregation
From 1 comment
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…
ofek on HN
Questions
How test candidates are detected from a diff between commits
From 1 comment
What is "test candidates" and how are they detected from a diff between two commits?
throwaway290 on HN
Whether Datadog account is needed or just Jira/GitHub
From 1 comment
Do I need to be a datadog user for this, or just a Jira/Github user?
_joel on HN
Whether teams use PR-to-test-ticket workflows
From 1 comment
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…
tootie on HN
Alternatives named
Ticket-based flow from grooming to dev, code review, then QA
From 1 comment
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…
tootie on HN