The University of Western Australia
School of Computer Science and Software Engineering

School of Computer Science and Software Engineering

CITS5501 Software Testing and Quality Assurance

Useful links

Project Management Proverbs

Nothing is impossible for the person who doesn't have to do it themselves.

The sooner you begin coding the later you finish.

Any project can be estimated accurately (once it's completed).

The most valuable and least used WORD in a project manager's vocabulary is "NO".

The most valuable and least used PHRASE in a project manager's vocabulary is "I don't know".

You can con a sucker into committing to an impossible deadline, but you cannot con him into meeting it.

At the heart of every large project is a small project trying to get out.



Each student is required (either individually, or as part of a pair) to research a specialist area of software testing and quality assurance, and give a presentation on that topic. Topics are to be agreed on with the unit coordinator prior to week 12.

Note that:

  • The topic should clearly relate to software testing and quality assurance
  • Presenters should allow 10 minutes for the presentation, and 5 minutes for questions
  • Exact presentation times will be randomly allocated
  • The presentation may use slides, software demonstrations, or white board presentations.
  • Material presented should be evidence-based (rather than simply matters of opinion)

Students are required to submit a short (no longer than one page) overview of their talk, prior to the presentation date. It should specify:

  • the title of the talk, and names and student numbers of presenters
  • an abstract motivating the topic and describing any main points
  • references and suggested further reading on the topic.


Presentations are assessed on three criteria:

  • Does the talk provide technical detail on the topic, at a level which can be understood by an audience of CITS5501 students?
  • Does the talk explain why the topic is relevant or useful to someone interested in testing and/or quality assurance?
  • Are the presenter(s) able to answer questions about the area?

Seminar schedule

Tuesday 22/5

Time Seminar


Ammar Abu Shamleh and Jye Dewar – Quality Assurance in the video game industry. What sets it apart?


Brian Lee and Zen Ly – Symbolic Execution


Zhisheng Xie – Continuous Integration and Continuous Deployment


Alex Arnold and Diva Lonial – Managing Technical Debt


Mengna Li and Lijie Liu – QA and testing of a live streaming video platform

Thursday 24/5

Time Seminar


Sanabel Abu Jwade and Jiaranai Keatnuxsuo – AI-Based Software Defect Predictors: Applications and Benefits in a Case Study


Eleanor Leung – QA and Testing of Machine Learning Systems


Chengchao Hong and Bin Cui – Software testing in mobile applications


Harpreet Kaur and Daniel Esquer – Testing of Medical Software

Tuesday 29/5

Time Seminar


Mark Robson and Michael Finn – Effectiveness of Mutation Testing


Zhiwei Huang and Kehan Dong – Time spent on software testing in a project


Guanheng Zhong and Qiuye Shen – Code Coverage; a Case Study of Simulation Software


Scott McCormack and Prabhanjan Veeravilli – Quality Assurance Practices in Agile Methodologies


Craig Brogle – Reproducible Integration Testing Against Real Databases


Spandana Vadde and Vishnu Prem Sanketh Galla – Photometric quality measures on effective face recognition


Wojciech Slabik and Ivory Lu – Test Driven Development Techniques and Strategies



Thursday 31/5

Time Seminar


Qianwen Lu and Jiaqi Han – A genetic programming approach to automated software repair


Ankita Bhagat and Sukhvinder Kour – Agile Formal Methods


Zhouyuan Qin and Prerna Toppo – The psychology and economics of software testing quality


Alexander Emery – Role of devops in QA


Thomas Ankers and Damon van der Linde – Quality Assurance of Safety Critical Systems.


James Ellisdon – Using machine learning to generate tests


Yuntian He and Anupam Anupam – Stress Testing