Reviewing AI-generated code — Technical https://thesis.uya.no/proposals/review-with-reasons/#technical-track BACHELOR Final result: A review prototype and concrete usability fixes. Task: Build a code-review screen with links to tests and source lines. Data: HumanEval/0–39 + Qwen Coder completions (mixed) finalise model revision and prompt; save one greedy completion per task. Prepare independent requirement-based audit tests before generation; retain failed outputs. Requires: Inference compute, developers and independent correctness review; no unseen-task or general model-performance claim. Method: Use the fixed HumanEval completions and independent audit tests; observe reviewers detecting and explaining faults. Plan 4 participant sessions. STEPS Build and test 1. Read the starting sources and choose one established implementation method. 2. Write the requirements, data fields, system diagram and test cases. 3. Prepare HumanEval/0–39 + Qwen Coder completions. Make the answer key and pass criteria before testing. 4. Build a working version of a review prototype and concrete usability fixes. 5. Run function, integration and failure-case tests. Record each result. 6. Run the practical evaluation and list the changes the system still needs. MASTER Final result: Review screen, completions and acceptance-error results. Research question: Investigate whether evidence links improve detection of AI-code faults or reinforce misleading tests. Use independent audit tests and unchanged generated outputs; analyse natural error types and reviewer verification behaviour separately. Research result: An evaluation linking test adequacy, traceability and human review effectiveness. STEPS Design, build and test (DSR) 1. Read the newest papers and list the closest existing systems. 2. Write down the versions, fields, data split, case assignment, random seeds and correct answers for HumanEval/0–39 + Qwen Coder completions. 3. Draw the user workflow, data model and system architecture. List the requirements and pass criteria. 4. Build a working version of review screen, completions and acceptance-error results. 5. Test every function, connection and failure case. Save the failed tests as well as the passed tests. 6. Compare the system with the named alternative. Then run the user task or decision task in the assignment. 7. Report the measured result, the failed cases and the design lessons another team can reuse. CURRENT PROJECT LITERATURE LLM-Based Test-Driven Interactive Code Generation: User Study and Empirical Evaluation (2024, peer-reviewed): https://doi.org/10.1109/TSE.2024.3428972 Shows that test-mediated interaction can improve evaluation of AI-generated code. Can LLM Replace Stack Overflow? A Study on Robustness and Reliability of Large Language Model Code Generation (2024, peer-reviewed): https://doi.org/10.1609/aaai.v38i19.30185 Demonstrates that executable generated code can still contain substantial API misuse. IS THEORY STARTING POINTS Liu et al. (2023) — Is Your Code Generated by ChatGPT Really Correct?: https://proceedings.neurips.cc/paper_files/paper/2023/file/43e9d647ccd3e4b7b5baab53f0368686-Paper-Conference.pdf Distinguish passing a public test suite from independently assessed correctness. Vasconcelos et al. (2023) — Explanations Can Reduce Overreliance: https://doi.org/10.1145/3579605 Compare verification cost with trust as explanations of observed decisions. 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 How does test evidence change developers’ acceptance of AI-generated functions? EXAMPLE TOOLS Qwen2.5-Coder-7B-Instruct, Python, HumanEval, Streamlit Equivalent tools are fine. FIRST THREE ACTIONS 1. Download HumanEval and the named model; record revisions, prompt and decoding settings. Confirm access to inference compute and record model, software and hardware versions. 2. Generate tasks 0–2 and run the published tests in an isolated environment with no credentials. 3. Prepare the same code-review layout in both conditions; show either raw pytest logs or line-linked requirement and test evidence while keeping code and executed tests unchanged. LITERATURE SEARCH AI generated code review trust test evidence DATA HumanEval/0–39 + Qwen Coder completions (mixed) finalise model revision and prompt; save one greedy completion per task. Prepare independent requirement-based audit tests before generation; retain failed outputs. HumanEval: https://github.com/openai/human-eval Qwen2.5-Coder-7B-Instruct: https://huggingface.co/Qwen/Qwen2.5-Coder-7B-Instruct Transformers generation settings: https://huggingface.co/docs/transformers/main_classes/text_generation HOW TO TEST IT Report the 40-completion published-test pass fraction separately. Eight developers review 10 non-overlapping cases using either raw pytest logs or line-linked requirement and test evidence, with code and executed tests unchanged. Score false acceptance/rejection against independently verified faults, plus time and requests for more checking. FINAL RESULT Review screen, completions and acceptance-error results. ACCESS OR PEOPLE Inference compute, 8 developers and independent correctness review; no unseen-task or general model-performance claim. TEMPLATES https://thesis.uya.no/starters/review-with-reasons/technical/data-plan.csv https://thesis.uya.no/starters/review-with-reasons/technical/evaluation.csv https://thesis.uya.no/starters/review-with-reasons/technical/literature-matrix.csv Use participant codes instead of names or email addresses.