1{2 "model": "claude-opus-4-8",3 "should_trigger_pass_rate": 1.0,4 "should_not_trigger_pass_rate": 1.0,5 "should_trigger_pass": "10/10",6 "should_not_trigger_pass": "10/10",7 "results": [8 {9 "query": "should I add integration tests for the SsoController change, or are unit tests enough?",
16 "query": "what's the right test strategy for the billing webhook handler, testing trophy or pyramid?",
17 "should_trigger": true,
18 "triggers": 7,
19 "runs": 7,
20 "trigger_rate": 1.0
21 },
22 {
23 "query": "which layer should the passkey enrollment validation test live at: unit, component, or E2E?",
24 "should_trigger": true,
25 "triggers": 7,
26 "runs": 7,
27 "trigger_rate": 1.0
28 },
29 {
30 "query": "PM-32009 is the item-types import/export work. recommend which tests to add and at which layer for it.",
31 "should_trigger": true,
32 "triggers": 7,
33 "runs": 7,
34 "trigger_rate": 1.0
35 },
36 {
37 "query": "the coverage report for the org-vault export epic lists several behaviors with no automated tests. which layer should each new test target?",
38 "should_trigger": true,
39 "triggers": 7,
40 "runs": 7,
41 "trigger_rate": 1.0
42 },
43 {
44 "query": "I've got a Testmo CSV of manual cases for the vault-unlock rework. which of these should be automated and at which layer?",
45 "should_trigger": true,
46 "triggers": 7,
47 "runs": 7,
48 "trigger_rate": 1.0
49 },
50 {
51 "query": "the autofill refactor PR in bitwarden/clients has gaps. where should the new tests go to keep the pre-merge gate deterministic?",
52 "should_trigger": true,
53 "triggers": 7,
54 "runs": 7,
55 "trigger_rate": 1.0
56 },
57 {
58 "query": "do we need an E2E for the billing upgrade flow, or can component tests cover it?",
59 "should_trigger": true,
60 "triggers": 7,
61 "runs": 7,
62 "trigger_rate": 1.0
63 },
64 {
65 "query": "recommend a test layering for the emergency-access revamp so the pipeline can gate on it",
66 "should_trigger": true,
67 "triggers": 7,
68 "runs": 7,
69 "trigger_rate": 1.0
70 },
71 {
72 "query": "what's the lowest layer that can own the CipherService.RestoreAsync validation logic?",
73 "should_trigger": true,
74 "triggers": 7,
75 "runs": 7,
76 "trigger_rate": 1.0
77 },
78 {
79 "query": "which behaviors in bitwarden/server PR 6001, the billing webhook handler, already have test coverage today?",
80 "should_trigger": false,
81 "triggers": 0,
82 "runs": 7,
83 "trigger_rate": 0.0
84 },
85 {
86 "query": "write manual Gherkin test cases for PM-35944 that I can import into Testmo",
87 "should_trigger": false,
88 "triggers": 0,
89 "runs": 7,
90 "trigger_rate": 0.0
91 },
92 {
93 "query": "write the unit tests for the new CipherService.RestoreAsync method",
94 "should_trigger": false,
95 "triggers": 0,
96 "runs": 7,
97 "trigger_rate": 0.0
98 },
99 {
100 "query": "the sync E2E in bitwarden/test keeps timing out in CI, help me fix the flaky test",
101 "should_trigger": false,
102 "triggers": 0,
103 "runs": 7,
104 "trigger_rate": 0.0
105 },
106 {
107 "query": "run the jest suite for bitwarden/clients and tell me which specs are failing",
108 "should_trigger": false,
109 "triggers": 0,
110 "runs": 7,
111 "trigger_rate": 0.0
112 },
113 {
114 "query": "refactor these xUnit tests to use the new shared fixture pattern",
115 "should_trigger": false,
116 "triggers": 0,
117 "runs": 7,
118 "trigger_rate": 0.0
119 },
120 {
121 "query": "review bitwarden/server PR 5821 for bugs and security issues before I approve it",
122 "should_trigger": false,
123 "triggers": 0,
124 "runs": 7,
125 "trigger_rate": 0.0
126 },
127 {
128 "query": "what's the overall code-coverage percentage on bitwarden/server right now?",
129 "should_trigger": false,
130 "triggers": 0,
131 "runs": 7,
132 "trigger_rate": 0.0
133 },
134 {
135 "query": "what test coverage already exists for the surfaces in the emergency-access revamp Tech Breakdown doc (bitwarden/tech-breakdowns)?",
136 "should_trigger": false,
137 "triggers": 0,
138 "runs": 7,
139 "trigger_rate": 0.0
140 },
141 {
142 "query": "explain how the testing trophy works and when you'd pick it over a pyramid",