CSCI926 Software Testing and Analysis Assignment

CSCI926 Software Testing Analysis Assignment

CSCI926 Software Testing and Analysis Assignment

This CSCI926 software testing and analysis assignment that project title is quality assessment of commercial search services.

1. Size of a group: minimum four, maximum six.

2. Progress report: Each group is required to give a 3-minute oral report to the tutor/lecturer in Week 4 lab, and submit a one or two pages’ progress report. All team members are required to attend.  The progress report should cover the following points:
Every team member’s name, email address and student number.

  1. What is your progress so far?
  2. Did you encounter any problems?
  3. Your future plan and timetable.

3. Assessment of individual team members:

Each team member is assessed individually based on his/her individual contribution. Basically, the “individual contribution” of each team member is assessed by all the other team members in terms of “contributed”, “very little”, and “almost no contribution”. For a team member who has “contributed”, he/she will receive 100% of the group marks; for a member who contributed “very little”, he/she will receive 50% of the group marks; for students who made “almost no contribution”, he/she will receive 0 marks for the group project. Details of individual contributions for each team member must be printed on the cover page of the final project report. In some situations, the above criteria may be adjusted by your lecturer.

4. Marking criteria

1. Progress report
2. Final presentation
Submit a hardcopy of your presentation slides to the lecturer/tutor immediately before your group’s presentation. It is not compulsory for all team members to speak, but all team members must stand in front of the class during their group’s presentation. If a student is absent from his/her group presentation, the student will receive 0 presentation marks.

3. Did you use a folder to enclose all submitted materials when you submit the final report in week 13 lecture?
4. Technical value and writing of the final project report (due at the start of week 13 lecture)

5.Technical tasks

Step 1: Conduct in-depth study of the following paper (available in Moodle site under “Readings”). Also read related papers when needed.
[1] Z. Q. Zhou, S. Xiang, and T. Y. Chen, “Metamorphic testing for software quality assessment: A study of search engines,” IEEE Transactions on Software Engineering, vol. 42, no. 3, pp. 264–284, 2016.

Step 2: Conduct automatic software testing of ALL of the following websites by applying and extending the metamorphic testing (MT) approach introduced by Zhou et al. [1]. Report your results. (Note: If your group is not capable of testing all six websites, the scope can be compromised. This, however, might cause a deduction of marks.)

Detailed marking criteria of technical tasks (42 marks)

  1. Identification of software quality characteristics to be investigated for each website (you could identify the same or different quality characteristics for different websites). (2 marks)
  2. Identification and implementation (automation) of a set of valid metamorphic relations (MRs) for each website and each quality characteristic. (10 marks)
  3. Automatic generation and execution of a large number of test cases as well as automatic checking of the test results. (Note: How large is “large”? It depends on your resources.) (10 marks)
  4. Data analysis of test results for each website and comparison of software quality characteristics of different websites based on your test results. (10 marks)
    Example of comparison: vs on a common set of software quality characteristics (e.g., reliability).
  5. Detection of real-life bugs. (Screenshots must be provided as evidence of bugs. Number of bugs, variety of bugs, and seriousness of bugs will be considered.) (10 marks)