Assignment 2. System Test

Description

During this exercise, you will write a testing strategy for an application given a scenario, requirements and source code.
Then you will plan how the testing should be done.
You will also write Manual test cases and finally conduct testing of the application and report the results.

Note that you do not need to fix any bugs or adress the problems you find in this assignment, you do however need to run the system and test it.

Group Assignment and Individual assignment

This exercise contains three tasks. The first task can be done by a single student, or in a group of 1-4 students. Task two and three elements should be done individually.

Goals

This assignment aims to reach the following objectives from the syllabus:

Upon completion of the examination, students should be able to:

  • individually explain, apply, automate and document common software testing methods and techniques
  • individually or in a group plan, document, and execute software testing for a small software product
  • describe and explain software testing in a software development process context
  • define fundamental concepts such as requirement, error, quality, traceability, reproducibility, exit criteria and failure rate

The assingment aim to practice the following content from the syllabus

  • Testing methods and techniques
  • Testing in the software development process
  • Regression testing
  • Acceptance testing
  • Analysis, communication, and documentation of software tests and test results

Theory

Aditya P. Mathur, “Foundation of Software Testing” Chapter 1 & 2

Read up on Exploratory Testing
http://en.wikipedia.org/wiki/Exploratory_testing

Test strategy
http://en.wikipedia.org/wiki/Test_strategy

Use-Cases
Writing effective Use-Cases

Web application Security testing
https://www.owasp.org/index.php/Web_Application_Security_Testing_Cheat_Sheet

James Bach on Software Testing

And lecture content…

Task 1 of 3.

This part of the assignment may be done in a group of one to four students. Every student must be active in the construction of the artifacts.

Scenario

The small Software Development Company (SDC) has found a possible market niche for giving out a simple to deploy web-server. SDC aims to redistribute this server on a wide range of Internet Of Things (IOT) to present information from sensors etc. SDC wants an easy to deploy java-web-server that can be deployed on many different devices and therefore that can attract attention of a wide range of IOT developers. IOT-developers want minimal configuration as well as easy integration and adaptation of the web-server. End-customers want easy access and absolute security. The SDC management has found an open source abandonware software called “My web server”. It is your job as SDC employee(s) to evaluate the current state of “My web server”. SDC needs to know if the abandoned software fulfills the requirements as stated in the requirement document. Your budget is one man-week times the number of students. SDC management want a strategy, plan, test-cases as well as a test-report.

Requirements and source code:
Requirements
Application Source Code

Todo: list

  • Write a test-strategy for the application.
  • Write a test-plan for the application for current iteration
  • Write manual test cases for the application
  • Execute the test-plan (test the software)
  • Report the result of testing in a test report.

Deliverables

Hand in your strategy, test-plan, test-cases and test-report as and upload those as four .pdf files that you zip and upload into the Peer Review system before the deadline.

  • strategy.pdf
  • testPlan.pdf
  • testCases.pdf
  • testReport.pdf

all of these are zipped and uploaded as a single .zip file

Important notes on how to prepare and handin the artifacts:

  • The strategy, test-plan, test-cases and test-report should be in .pdf format and uploaded as a single zip file
  • The document should be anonymous, no names or traces of who you are should be in the document. Instead use role-names like “test-lead”, “scrum-master” or “product-owner”. The document and other text are not anonymous to course management.
  • All students in the group should upload the exact same document, please make sure that if you update the document and resubmit that all students update it.
  • The document or parts of it may not be shared between groups.
  • Read the review task in order to find out more about how to write a successful document.

External link to CSQUIZ


You need to log in and be registered on the course to do this assignment.

Task 2 of 3, Write Reviews of other groups work.

Give constructive reviews on other Students Test-Strategies-Test-Plan, Test-Cases and Test-Reports using the peer-review system.
The feedback should be anonymous, no names or traces of who you are should be in them. It is however not anonymous to course management.
Be helpful and nice.

The more reviews of high quality you submit the higher the chance of getting a good grade, see grading. After the second task, the examiner will check reviews and may fail reviews that are considered not valid and truthful. This means that if your review is removed you might not get a grade unless you have submitted more reviews.

Review the Clarity

Review the ease of which the document can be read and understood.

  • Language – Should be English. Issues can be related to Spelling or Grammar
  • Format and layout – The document uses pdf. It uses Tables, Links, Titles of different levels when appropriate
  • Disposition – The order of chapters or sections follow naturally so that they can be read from top to the bottom. The chapters are divided into paragraphs of text with a title.

Review the Completeness

Review that all parts of the document exists and that each part actually contains what it should

  • Test Strategy
    • Does the strategy describe stakeholders and their testing goals?
    • Does the strategy describe the available resources?
    • Does the strategy describe how the stakeholders testing goals are to be fulfilled by the plan?
  • Test Plan – Should describe and outline the current iteration’s test effort(Who does what when).
    • Does the test-plan describe what requirements that should be tested?
    • Does the test-plan describe what requirements that should NOT be tested?
    • Does the test-plan describe how testing should be done? at what test-level?
    • Does the test-plan describe who should do different activities? (responsibilities)
  • Manual Test Cases
    • Are the manual test-cases traceable to which requirement that is tested?
    • Do each manual test-case describe, input and expected output? (when relevant)
  • Test Report
    • Does the test-plan show what has been tested and not tested?
    • Does the test-report show which tests that fail or succeed?
    • Is there testing the other group should have done?

Review the Content

Review the test effort by the other group. Has the other group done a good job reporting their testing of the product?

Ambition and test-effort

  • Has the other group done a good job testing of the product, given the resources?
  • Do the manual test-cases cover all relevant scenarios in the use-cases?
  • Do the test-effort cover the relevant requirements?

Comment on what parts you think was good, what parts that could be improved and how to improve them:

Task 3 of 3. Give feedback on reviews.

You should receive and respond to the reviews given to you providing feedback and also grade the reviews usability for you.
This task should be done individually. All reviews that are submitted before deadline task 2 must be responded to at deadline task 3 (see study guide). Report if the review your test plan is not a complete review or if the reviewer has done a good job! Be nice and truthful, while it is anonymous to the authors of the review, you are not anonymous to course-management.

Grading

This assignment is graded A-F. The grading is done individually.

All three tasks must be done to be graded.

  1. Student has uploaded a document
  2. Student has submitted reviews
  3. Student has responded to reviews

Two different grades will be combined one for the test plan and one for the peer reviews.

Test plan part decides 50% of the grade. The test-plan is graded depending on the median grade from all “approved” reviews. Each review has three grades so with two reviews the median grade is extracted from 6 gradings. If no reviews are remaining (for example if the examiner fails all reviews of your document, the examiner will conduct a single review that will determine the grade.

  • E. The median review grade is sufficient
  • C. The median review grade is good
  • A. The median review grade is excellent

Peer review part 50% of the grade comes from providing useful reviews. This part of the grade is determined by the feedback given by the students who wrote the test plan. Note that if the examiner removes one of your reviews, that review is no longer counted.

  • E. The student has conducted at least 2 peer reviews, at least two marked as sufficient by the authors
  • D. The student has conducted at least 3 peer reviews, at least one marked as good and two as sufficient by the authors
  • C. The student has conducted at least 3 peer reviews, at least three marked as good by the authors
  • B. The student has conducted at least 4 peer reviews, at least one marked as excellent, two as good by the authors
  • A. The student has conducted at least 4 peer reviews, at least 2 marked as excellent, two as good by the authors

A test plan or a peer review marked as failed or not even an attempt will be examined by the teachers who can choose to override reviews and feedback. This will also be the case when there is a conflict between reviewer and author or a large spread in scoring. This means that the examiner uses the reviews and review responses as guidelines for the final grade.
The grade of the assignment will be reported in Ladok, when the final exam is completed and examined.

A second attempt will be given during spring with a new document on another software. Failing to complete the assignment will result in a re-exam next time the course is given.

Welcome to CoursePress

en utav Linnéuniversitets lärplattformar. Som inloggad student kan du kommunicera, hålla koll på dina kurser och mycket mer. Du som är gäst kan nå de flesta kurser och dess innehåll utan att logga in.

Läs mer lärplattformar vid Linnéuniversitetet

Student account

To log in you need a student account at Linnaeus University.

Read more about collecting your account

Log in LNU