← All proposals
Illustration: Software-development information-system concept: Review with reasons

Reviewing AI-generated code

Measure whether test evidence helps developers reject faulty AI-generated Python functions.

Download brief

Technical

Bachelor’s · applied project

Final result

A review prototype and concrete usability fixes.

02

What to do

  • Build a code-review screen with links to tests and source lines.
03

How it is tested

Use the fixed HumanEval completions and independent audit tests; observe reviewers detecting and explaining faults. Plan 4 participant sessions.

04

Before you start

Example tools · Qwen2.5-Coder-7B-Instruct, Python, HumanEval, Streamlit These are suggestions; equivalent tools are fine.

Access or people · Inference compute, developers and independent correctness review; no unseen-task or general model-performance claim.

Research method · Build and test · 6 steps
  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.
Download the complete bachelor planDownload bachelor instructions

Master’s · research project

Final result

Review screen, completions and acceptance-error results.

02

What to do

  • finalise HumanEval completions with model/tokenizer SHA, runtime, quantization, prompt, greedy decoding, seed and output limit; run them only in an isolated sandbox.
  • Compare raw pytest logs with line-linked requirement/test evidence while keeping code and tests identical; create independent audit tests and a fault taxonomy.
  • Report public-test pass rate separately from false acceptance/rejection, fault detection, evidence navigation and time; verify capture determinism and test independence.
03

How it is tested

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.

04

Before you start

Example tools · Qwen2.5-Coder-7B-Instruct, Python, HumanEval, Streamlit These are suggestions; equivalent tools are fine.

Access or people · Inference compute, 8 developers and independent correctness review; no unseen-task or general model-performance claim.

01—03

Start with these 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.
Files, questions and sources

Pilot question: How does test evidence change developers’ acceptance of AI-generated functions?

Literature search: AI generated code review trust test evidence

Download starter instructions
Research method · Design, build and test (DSR) · 7 steps
  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.
Research question and sources

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.

Current project literature

IS theory starting points

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.

Search terms: AI generated code review trust test evidence

Non-technical

Bachelor’s · applied project

Final result

A review checklist grounded in observed mistakes.

01

Material to create

12 printed Python packets

6 checked-correct and 6 faulty functions; 3 faults are missed by displayed tests. Hide labels and keep code identical between evidence-present/absent versions.

02

What to do

  • Identify the checking steps Python-capable final-year IS students use when reviewing AI-generated code.
03

How it is tested

Use printed code/test packs in think-aloud sessions; classify missed checks and useful evidence. Plan 4 participant sessions.

04

Before you start

Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.

Access or people · Recruit Python-capable final-year IS students. Reading code is required; writing software is not.

Research method · Study and improve · 6 steps
  1. Read the starting sources and write the exact information problem.
  2. Prepare 12 printed Python packets 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 review checklist grounded in observed mistakes. List the three most useful changes.
Download the complete bachelor planDownload bachelor instructions

Master’s · research project

Final result

Review checklist and findings on misplaced trust.

01

Material to create

12 printed Python packets + 8 Python-capable final-year IS students

6 checked-correct and 6 faulty functions; 3 faults are missed by displayed tests. Hide labels and keep code identical between evidence-present/absent versions.

02

What to do

  • Prepare paper review packets containing a function, requirement and test report.
  • Ask developers whether they would approve it, then interview them about trust in AI code.
03

How it is tested

Python-capable final-year IS students approve, reject or defer on non-overlapping packets. Compare per-person decision errors and reliance on displayed tests versus independent inspection; no model execution or interface development.

04

Before you start

Example tools · LibreOffice Writer/Calc, audio recorder with consent; no programming required. These are suggestions; equivalent tools are fine.

Access or people · Recruit 8 Python-capable final-year IS students. Reading code is required; writing software is not.

01—03

Start with these three actions

  1. Prepare a pilot with 2 of the 12 printed Python packets. Recruit 8 Python-capable final-year IS students for the full study; write the task questions and independent 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.
Files, questions and sources

Pilot question: When do reviewers rely on test results despite remaining gaps in verification?

Literature search: AI generated code review trust test evidence qualitative scenario study

Interview prompts

  • Would you approve this function and why?
  • Which behaviour do the tests actually cover?
  • What would you check before relying on the AI output?
Download starter instructions
Research method · Study, compare and explain · 7 steps
  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 printed Python packets + 8 Python-capable final-year IS students.
  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.
Research question and sources

Research question: Explain overreliance on plausible AI code among novice reviewers despite contradictory evidence. Contrast verification-cost and competence-belief explanations using task observations and follow-up interviews.

Research result: A specific account of evidence use in novice AI-code review.

Current project literature

IS theory starting points

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.

Search terms: AI generated code review trust test evidence qualitative scenario study

Your degree, track and shortlist are saved in this browser.