Choosing which tests run first — Non-technical https://thesis.uya.no/proposals/test-what-matters-first/#nontechnical-track BACHELOR Final result: A clearer test-report template and release checklist. Task: Find which information developers need in a partial test-run report. Data: 12 CI reports (planned) 4 complete passes, 4 partial runs, 2 failures and 2 timeouts. Supply one explicit release policy and deadline; hide the reference decisions. Requires: Recruit developers; use prepared reports, no CI implementation. Method: Use the paper run summaries and an explicit release policy; observe release decisions and document misunderstandings. Plan 4 participant sessions. STEPS Study and improve 1. Read the starting sources and write the exact information problem. 2. Prepare 12 CI reports and a separate answer sheet or coding sheet. 3. Run one pilot and fix unclear questions. 4. Collect the named evidence with consent. 5. Group the findings with the stated categories and check the answer sheet. 6. Produce a clearer test-report template and release checklist. List the three most useful changes. MASTER Final result: CI reporting checklist and analysis of merge decisions. Research question: Explain when partial test results are treated as sufficient release evidence. Use the same release policy across scenarios; compare verification effort, report representation and responsibility as other explanations. Research result: A specific account of release confidence under incomplete testing evidence. STEPS Study, compare and explain 1. Read the newest papers and write one exact research question. 2. State which people, cases or documents you will study and what you will compare. 3. Write the selection rules, questions and analysis steps for 12 CI reports + 8 developer interviews. 4. Run one pilot. Fix unclear questions or categories, then keep the guide unchanged. 5. Collect the named interviews, cases or documents with consent. 6. Analyse them with the stated comparison or coding method. Keep disagreements and missing data. 7. Report the answer, the evidence and the practical output named in the assignment. CURRENT PROJECT LITERATURE Faster Feedback with AI? A Test Prioritization Study (2024, peer-reviewed): https://doi.org/10.1145/3660829.3660837 Compares modern and simple test-prioritization methods using change-based mutations. Feature-oriented test case selection and prioritization during the evolution of highly-configurable systems (2024, peer-reviewed): https://doi.org/10.1016/j.jss.2024.112157 Provides current evidence on selection overhead and failure detection under test budgets. IS THEORY STARTING POINTS Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance: https://doi.org/10.1145/3579605 Compare verification cost with trust as explanations of observed decisions. Orlikowski & Gash (1994) — Technological Frames: https://dl.acm.org/doi/10.1145/196734.196745 Compare how roles interpret the purpose, operation and use of the same system. Search Scopus or Web of Science and ACM Digital Library using the topic query, then follow citations to the thesis start date. Record searches and compare methods, data, findings and limitations in literature-matrix.csv. Use that review to confirm or revise the gap and choose a current comparator. The linked papers are starting points. PILOT QUESTION Which missing CI evidence changes a developer’s decision to merge under a deadline? EXAMPLE TOOLS LibreOffice Writer/Calc, audio recorder with consent; no programming required. Equivalent tools are fine. FIRST THREE ACTIONS 1. Prepare a pilot with 2 examples from: 12 fictional CI reports + 8 developers. Write the task questions and a reference answer sheet. 2. Write a recruitment message, information sheet and consent form for the participants named above. Agree privacy handling with the supervisor before contact. 3. Pilot one session after approval; revise unclear questions, finalise the task sets and coding categories, then recruit the planned sample. INTERVIEW QUESTIONS - Would you merge this change now? - Which behaviour remains unchecked? - Which missing result would change your decision? LITERATURE SEARCH continuous integration test prioritisation developer feedback decisions qualitative scenario study DATA 12 CI reports + 8 developer interviews (planned) 4 complete passes, 4 partial runs, 2 failures and 2 timeouts. Supply one explicit release policy and deadline; hide the reference decisions. HOW TO TEST IT Compare raw reports with identical evidence highlighting completion status. Count policy-unjustified merges and perceived risk, missing evidence and escalation reasoning; partial runs are not inherently unsafe. FINAL RESULT CI reporting checklist and analysis of merge decisions. ACCESS OR PEOPLE Recruit developers; use prepared reports, no CI implementation. TEMPLATES https://thesis.uya.no/starters/test-what-matters-first/nontechnical/study-plan.csv https://thesis.uya.no/starters/test-what-matters-first/nontechnical/coding-sheet.csv https://thesis.uya.no/starters/test-what-matters-first/nontechnical/literature-matrix.csv Use participant codes instead of names or email addresses.