Product tour · QA / test lead
Your test rules checked on every pull request, and a merge check that holds.
See a rule written in plain words and applied to the next pull request, a false positive dismissed once, and a goal tracked across pull requests.
The product tour for your role: PDF·PowerPoint
QA lead
A rule of your own: no test skipped without a ticket
As a QA lead, I want a pull request that skips a test held unless it names a ticket, so coverage does not erode one test at a time.
A skipped test passes CI. Nobody notices it in review, and nobody turns it back on.
What to notice
- Anyone with the right role can write a rule. The next review checks it, with no code to write.
- A rule applies to the packs you pick: here, TypeScript files.
- HIGH and CRITICAL findings hold the merge. Lower ones only show in the review.
Step 1 of 4
A QA lead writes a rule: no test is skipped without a ticket.
The QA lead writes the rule in plain words: what to flag, its severity, and the files it applies to.
Reviewer
Dismiss a false positive once
As a reviewer, I want to dismiss a false positive with a reason, so it does not come back after every push.
Most review tools forget. The same false positive comes back on the next commit, and people start to ignore the tool.
What to notice
- The note stays with the finding, for the next reviewer and for audits.
- Each decision counts against the rule. When reviewers often reject a rule, OpenTremor suggests a change to it.
Step 1 of 3
Every pull request is reviewed against your rules.
OpenTremor's comment on the pull request lists two findings: the customer data bug and a slow, blocking call in a script.
Tech lead
Every pull request checked against your team's rules
As a tech lead, I want every pull request checked against our written standards, so reviewers stop repeating the same comments.
Your standards are in a wiki and in people's heads. A pull request follows them only if the reviewer knows them and has time.
What to notice
- The rule is your team's own, written in plain words. You do not need a special rule language.
- The finding explains the risk, not only the line of code.
- The fix is a normal GitHub suggestion. OpenTremor never commits code for you.
Step 1 of 5
A developer opens a pull request.
The pull request adds a list of invoices. Its database query returns the invoices of all customers, not only the caller's.
Engineering director
Track an engineering goal across pull requests
As an engineering director, I want to know if our changes move us toward our goals, not only if they fix single issues.
Goals like customer data isolation or a migration live in a slide deck. Nobody knows the real progress, and nobody sees when a pull request makes it worse.
What to notice
- A measured step is done when its rules have no open findings left in the product.
- One pull request never completes the goal by itself. A step is done when its count reaches zero, or when a person marks it as done.
Step 1 of 4
An engineering director sets a goal, with a step OpenTremor can measure.
The goal "Tenant isolation everywhere" has a step that OpenTremor measures: the number of open findings for one rule. A scan found one.
Try it on your own pull requests.
Connect a repository, write one rule, and open a pull request.