Computer Science Question

CR084_ISYS1085_A4-need introduction and scope sections,3 pages report , 2slides +300words script for presentation

RMIT Classification: Trusted
ISYS1085/ISYS1087 Software Testing (Assignment 4: Industrial Case Study)
BACKGROUND:
Using RTI International’s internal research funds, Tangerine launched in 2011 as open-source
software under a GNU General Public License. Since its inception, Tangerine has been used by
more than 50 organizations to conduct more than 1.5 million assessments and surveys in over
100 languages and 65 countries (predominately in Central America, Africa and Southeast Asia).
Tangerine was initially designed to facilitate the EGRA and EGMA methodologies that RTI
developed in 2006 under the U.S. Agency for International Development’s Education Data for
Decision Making (EdData) II project to assess numeracy and literacy in primary school (grades
one through four). RTI International’s commitment to improving early-grade reading in lowincome countries continues to be on the forefront of its agenda, and through the Tangerine
products RTI has been able to extend the use of EGRA and EGMA worldwide.
With the trio of Tangerine products – Tangerine, Tangerine: Class and Tangerine: Tutor – users
observe classrooms, conduct surveys, and administer EGRA and EGMA assessments orally (with
a paper prompt), measuring student ability through the offline mobile application. To ensure
precision of measurement, Tangerine’s built-in timer automatically records start and end times
for reading and math tests, and when internet becomes available, the user uploads the results
into comma-separated values (CSV) files available for analysis. Tangerine can be installed on any
device running Android version 2.3 or higher; recommended specifications include a minimum 6inch screen display, 1-GHz processor, 1 GB of RAM and a battery life of at least six hours.
Depending on their requirements, users can collect and store data on RTI’s server; however, as
Tangerine is open-source software, some organizations and Ministries of Education install the
open-source software code on their own website hosts.
Hypothetically, RTI is seeking independent testing services and is currently accepting proposals
for the project. You can read more about this project in [1] and [2]. You can be familiar with this
tool by watching this video.
TASK:
You are a boutique specialized software testing consultancy company, with 6 partners and you
want to participate in this tender. As a result, you must prepare a test plan using templates
provided in week 11 tutorial and provide an online presentation of 12 minutes discussing, at a
high level, the testing strategy that you propose to take if you are awarded the work.
REFERENCES:
1. https://techchangearticulate.s3.amazonaws.com/DIAL/SDG%20Framework/v15/story_html5.html,
retrieved October 8th, 2023
2. https://digitalprinciples.org/resource/tangerine-mobile-assessments-made-easy/ ,
retrieved October 8th, 2023
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
Assignment 4: Industrial Case Study (Team)
Start Assignment
Due Sunday by 11:59pm
Points 20
Submitting a file upload
Allowed Attempts 1
Available Oct 9 at 3pm – Oct 22 at 11:59pm
Attempts 0
Assessment task…
Assignment name: Industrial Case Study
Course code: ISYS1085/ISYS1087
Weighting: 20%
Due date: per Canvas due date
1. Course Learning Outcomes Assessed
This assessment supports the following learning outcomes:
CLO 4: Present a collaborative approach in groups to map out how the group (a pseudo-company)
hopes to attract the contract to perform the oversight of Software Testing for a project or company.
CLO 5: Communicate clearly and effectively using the technical language of the field correctly.
2. Overview of Assessment
This group assignment aims to evaluate your understanding of Software Testing. The goal is to test a
software system as a group of professionals for a (company) industry tender by applying the
accumulated knowledge. You are responsible for analyzing the testing needs for a specific scenario
and presenting your work.
https://rmit.instructure.com/courses/107474/assignments/839513
⻚页码：1/6
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
3. Assessment Tasks
1. The purpose of this assessment (https://rmit.instructure.com/courses/107474/files/34331137?wrap=1)
(https://rmit.instructure.com/courses/107474/files/34331137/download?download_frd=1) is to
examine whether you have assimilated all the accumulated knowledge surrounding Software
Testing in a way that you can apply this knowledge and respond to an industry tender to test a
software system in the guise of a (company) group of testing professionals.
2. You should form a group of 6 and must have your group and members registered on Canvas. You
may work with someone you know in the course. Otherwise, your tutor will help you form a group.
3. Each group will be a mock consulting test company responding to the tender described in the
assignment. The project you will be bidding for is detailed in the Assignment.
4. Your task will be to examine what the testing requirements are/should be and discuss your
company’s approach to the testing tender requirement. Then, you should prepare a test plan (refer
to the week 11 tutorial), create a PowerPoint file based on your approach, develop a group
presentation of a maximum of 12 minutes (with the camera on), and discuss your company’s
approach to the testing tender requirements.
5. You should draw from the learning outcomes that you have assimilated from:
lectures
tutorials
your own independent research
6. A good group will inevitably have questions of clarification. These should be emailed to
(mailto:golnoush.abaei@rmit.edu.au) the course coordinator, who will act as the client.
However, ensure you have read all the references in the assignment carefully before asking.
General questions could be asked in the Teams Channel.
4. Submission Instructions & Feedback
You need to submit
1. Test plan file in PDF format; you must rename it to yourGroupName-TestPlan.pdf.
2. A presentation file in PDF format, you need to rename it to yourGroupName-Slides.pdf.
3. Team Video with the mp4 format named as yourGroupName-Presentation.mp4. If your file size
is too big, upload it on your team-shared “One-drive” and provide a link to your recording on a
Word document named as yourGroupName-Presentation.docx and submit it. Please note that
all team members should present in the video recording with the camera on.
Submitting assignments other than the ones mentioned above will FETCH A ZERO for the
whole assignment.
5. Assessment Criteria
https://rmit.instructure.com/courses/107474/assignments/839513
⻚页码：2/6
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
Your report will be assessed based on the rubric at the end of this page.
Notes on final Mark:
18 – 20 Shortlisted
Your team has been shortlisted in the selection process to win the tender! Well done!
15 – 17 Longlisted
Your team came close to being shortlisted!
11 – 14 Qualified
Your team demonstrated comparable skills and knowledge to other qualified testers we have worked
with. You meet the core expectations we have of qualified testers, although we noted some major
areas of improvement.
0 – 10 Not meeting base requirements
While your presentation and effort were noted and appreciated, there were significant areas to work
on.
Late submission: If you submit your assignment late, your mark will be deducted (Unless special
consideration has been granted), based on how many days late it is.
-10% per day late
After 5 days, zero will be granted for the assignment submission
6. Academic Integrity
Academic integrity is about the honest presentation of your academic work. It means acknowledging
the work of others while developing your insights, knowledge and ideas. You should take extreme care
that you have:
Acknowledged words, data, diagrams, models, frameworks and/or ideas of others you have
quoted (i.e. directly copied), summarised, paraphrased, discussed or mentioned in your
assessment through the appropriate referencing methods,
Provide a reference list of the publication details so your reader can locate the source if necessary.
This includes material taken from Internet sites.
If you do not acknowledge the sources of your material, you may be accused of plagiarism because
you have passed off the work and ideas of another person without appropriate referencing, as if they
were your own.
RMIT University treats plagiarism as a very serious offence constituting misconduct. Plagiarism
covers a variety of inappropriate behaviours, including:
Failure to properly document a source
Copyright material from the internet or databases
https://rmit.instructure.com/courses/107474/assignments/839513
⻚页码：3/6
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
Collusion between students
For further information on our policies and procedures, please refer
to https://www.rmit.edu.au/students/student-essentials/rights-and-responsibilities/academicintegrity (https://www.rmit.edu.au/students/student-essentials/rights-and-responsibilities/academicintegrity)
7. Extension and Special Consideration
If you cannot submit an assessment on time due to circumstances beyond your control, you can
request an extension (up to five days). Applications must be submitted at least one business day
before the due date. (e.g. If an assessment is due on Sunday, students must submit a form by Friday).
To apply, please explain your situation in an email and send it to your tutor and cc the Course
Coordinator. You will be notified of the outcome within 48 hours.
Equitable learning adjustments/special considerations can be accommodated (e.g. extension of
time may be possible, or supplementary assessments arranged) by contacting the Course
Coordinator, Golnoush Abaei. If you are applying for extensions for your assessment within five
working days after the original assessment date or due date has passed, or if you are seeking an
extension for more than seven days, you will have to apply for Special Consideration unless there are
special instructions on your Equitable Learning Plan.
In most cases, you can apply for special consideration online
(https://specon.rmit.edu.au/specon/login.jsf) .
For more information on special consideration, visit the university website on special
consideration. (https://www.rmit.edu.au/students/student-essentials/assessment-andexams/assessment/special-consideration)
Industrial Case Study Assignment-2023
Criteria
Test Plan
Ratings
Pts
10 to >8.5 pts
8.5 to >6.5 pts
6.5 to >5.0 pts
5 to >2.5 pts
2.5 to >0 pts
Very good
Good
Average
Weak
NN
The test plan
The test plan
A team has
The team
Either a test
has been
has been
prepared the
has created a
plan was not
flawlessly
crafted by a
crafted
carefully by a
test plan, but
not all parts
test plan, but
unfortunately,
provided, or
the approach
team to
team to ensure
can meet the
most of it
to writing it
ensure that it
accurately
that it
accurately
unique
requirements
does not
meet the
was
incorrect.
addresses the
addresses the
of the case
unique
https://rmit.instructure.com/courses/107474/assignments/839513
⻚页码：4/6
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
unique
unique
study. While
requirements
requirements
requirements
some sections
of the case
of the case
study. Each
of the case
study. Most of
provide
detailed
study and is
not properly
section within
the sections
information for
explained or
the plan is
described in
within the plan
are described
executing the
plan effectively,
selected.
Although a
great detail,
in great detail,
improvements
few sections
providing all
the necessary
providing all
the necessary
are required to
customize the
provide
detailed
information
information
test plan for
information
required to
execute the
required to
execute the
this particular
case study.
for the
effective
plan
plan effectively.
10 pts
execution of
effectively.
the plan, the
content of the
test plan
should be
improved to
suit this
particular
case study.
Presenation
10 to >8.5 pts
8.5 to >6.5 pts
6.5 to >5.0 pts
5 to >2.5 pts
2.5 to >0 pts
Very good
Good
Average
Weak
NN
During the
Clear
Presentation is
Presentation
Presentation
presentation,
presentation of
not clear. Not
is not clear,
is very poor.
all team
members
the project. Not
all members
all members
participated or
not all
members
Not all
members
participated
participated, or
the quality of
participated
participated.
and delivered
an outstanding
the quality of
the
the
presentation of
or the quality
of the
Poor slides or
may not be
performance.
presentation of
team members
presentation
submitted.
The slides
were well-
the team
members was
is variable.
Very different
of team
members is
Poor time
management.
designed and
very different.
style of
variable.
submitted.
Time
Slides are
excellent and
presentation
within the
Slides are fair
and
management
submitted;
team. Good
submitted,
was excellent.
good time
management.
slides prepared
and submitted;
but
improvement
good time
is needed.
management.
Fair time
management.
https://rmit.instructure.com/courses/107474/assignments/839513
10 pts
⻚页码：5/6
Assignment 4: Industrial Case Study (Team)
2023/10/18 20(43
Total Points: 20
https://rmit.instructure.com/courses/107474/assignments/839513
⻚页码：6/6
Test Plan for
PROJECT A
​1​
© QATestLab All Rights Reserved
General information
Customer
Created by (Author)
Preparation date
Version
Status
Revision History
Version
Description
Author
Date
​2​
Approved by
Author
Date
© QATestLab All Rights Reserved
Summary
1.
Introduction
4
1.1. General information
4
1.2. Purpose
4
2.
Scope of project
4
2.1. Scope of web portal
4
2.2. Scope of mobile application
4
2.3. Scope of Admin part
5
3.
Work plan
5
4.
Test Plan and Strategy
5
4.1. Functional testing
5
4.2. Test Procedure
6
4.3. Bug Reports
7
5.
8
Resources
5.1. Tools
8
5.2. The list of the browsers
8
5.3. The list of the devices
8
7.
Testing Process Risks
8
8.
Test Team Expectations
9
9.
Responsibilities of Test Team Members
9
10. Deliverables
9
​3​
© QATestLab All Rights Reserved
1. Introduction
1.1. General information
This document describes the methods and procedures that will be used by the
QATestLab team in the functional testing process of the web and mobile applications.
It is meant to be used as a manual during testing works. It describes the procedure of
the testing process. The test plan is intended for project managers, product developers,
QA engineers.
The objective of the testing activities is to check functions and features of a software
product elaborated for web browsers (Chrome, Firefox, Edge, Safari) and modern
Android and iOS devices.
1.2. Purpose
This Test Plan document for the A project supports the following objectives:
●
Identify existing project information and software components to be tested.
●
Recommendation and description of the testing strategies to be employed.
●
Identify required resources and provide a test effort estimate
●
List the test project deliverable elements.
The results of test execution will be sent to the customer as reports. All found bugs will
be tracked using Trello bug tracker.
2. Scope of project
2.1. Scope of web portal
Testing of A is in the scope of this test plan. The following components and
functions would be tested:
1. Registration
2. Login and password recovery
3. Upload audio file
4. Payment
5. Social share function
6. Save and edit of user profile
2.2. Scope of mobile application
Testing of mobile application is in the scope of this test plan. The following
components and functions would be tested:
1. Create account using email
2. Create account using Social media accounts
​4​
© QATestLab All Rights Reserved
3. Login with 3 account types (Internal, External and Admin)
4. Password recovery
5. Play the audio files
6. Search for audio files
7. Add audio files to favorite list
8. Profile
2.3. Scope of Admin part
Testing of Admin part is in the scope of this test plan. The following components
and functions would be tested:
1.
Create account via backend
2.
Login as an admin
3.
Password recovery
4.
Upload audio files
5.
Edit information about the file
6.
Play the file
7.
Approve and reject new audio files
8.
Create external and internal users
9.
Collect statistic about played audio files
10. Collect statistic about files that were added to Favorite list
3. Work plan
The parties are agreed to follow the next work plan:
1. Test plan preparation
2. Test plan approval
3. Functional testing and bugs reporting
4. Daily reports preparation
5. Final report preparation
4. Test Plan and Strategy
1.1. Functional testing
The objective of functional testing is to make sure that the whole software product works
according to the requirements, and no significant errors appear in the application.
Functional testing is the most substantial part of software testing. It involves checking of
different aspects of the system. A software product must pass all the planned tests. Only
in this case its quality can be assured.
​5​
© QATestLab All Rights Reserved
Test Objective:
Ensure proper target-of-test functionality
Execute each use case, use-case flow, or function, using valid and
invalid data, to verify the following:
Technique:
●
The expected results occur when valid data is used.
The appropriate error or warning messages are displayed when
invalid data is used.
Each rule is properly applied.
●
The application construction is completed.
●
The test engineers are dedicated.
●
Necessary devices, instruments, and other equipment are acquired.
●
Test environment is prepared, and the application is released to the
test environment.
●
Test environment is prepared, and the application is released to the
test environment.
●
All the planned tests are performed.
There are no show-stopping errors.
All the errors of high priority and severity are fixed.
The test results are evaluated, discussed and approved.
●
●
Entry Criteria
Completion Criteria:
●
●
●
Special
Considerations:
None.
4.2. Test Procedure
Test procedure assumes the next points:
● Reporting of found software bugs.
Various aspects of the tested software should be checked; this requires executing of
different testing types.
The main testing type that would be executed:
● Functional Testing
● UI Testing
● Usability Testing
● Compatibility Testing (4 modern web browsers and devices)
● Regression testing
● Retesting (during the second round if needed)
It also will be checked how the software product is run on the browsers and devices that
are supposed to support it, how it starts and stops, how much time does it need to
launch.
​6​
© QATestLab All Rights Reserved
During this test round next types of testing will NOT be applied:
●
Security testing
4.3. Bug Reports
Bug reports are created in order to provide the development team and the project
managers with exhaustive information about the discovered defects. They must be
helpful in determining causes of the errors and correcting them.
Defect Severity can be classified into four categories:
●
Critical (blocker) defects are the failure of the complete software system or of a
critical subsystem, and no work or testing can be carried out after the occurrence of
the defect. It also applies to data loss failures and with processes that leave
inconsistent data stored on the database.
●
Major defects (and crashes) are those which also causes failure of entire or part of
the system, but there are some processing alternatives which allows further
operation of the system. It also applies to the system crashing, or aborting, during
normal operation of a non-critical flow.
●
Minor defects do not result in failure but causes the system to show incorrect,
incomplete, or inconsistent results.
●
Trivial defects are small errors that do not affect the functionality: typos, grammar
mistakes, wrong terminology, etc.
The information that is indicated in each bug report:
●
●
●
the software product name;
version number of the software product (if tested on mobile);
browser on which the tests were performed.
Each report provides the next information about the defect:
●
●
●
●
●
●
summary, which is short description of the problem;
location of the defect in the software product;
steps to reproduce the error;
frequency of the defect occurrence;
severity of the defect;
additional information about the defect in form of attached screenshots or video
records.
Third party software will be used for reporting and maintaining discovered errors. The
test team will log in that software all the defects that will be found during the testing
process.
​7​
© QATestLab All Rights Reserved
5. Resources
5.1. Tools
The following tools will be used for this project:
Name of process
Tool
Defect Tracking
Jira
Test Cases
Testrail
Snagit
Screenshots / Video capture
5.2. The list of the browsers
Name of browser
Version
Chrome
Latest
FireFox
Latest
Edge
Latest
Safari
Latest
5.3. The list of the devices
Name of device
OS
iPhone devices
All supported OS
Android devices
All supported OS
6. The criteria of quality
The product should operate in accordance with the requirements and the functional
specification (if present).
The product should not contain critical and blocking defects in the final version of the project.
7. Testing Process Risks
The next issues may influence testing works:
​8​
© QATestLab All Rights Reserved
●
changes and modifications of the software product that were not planned and discussed
with the test team beforehand;
●
changes in the software requirements that were not discussed with the test team
beforehand;
●
delays in correcting/fixing errors;
●
delays in delivering new builds to the test team.
8. Test Team Expectations
The test team must be provided with valid, updated documents during the whole testing
process.
All the required equipment, instruments, devices and software must be acquired and prepared
before beginning of the testing process.
All show-stopping errors must be corrected as soon as possible.
Release note should be added to each software release to the test team. The note must
explain which elements, functions and features were added to the program and how these
additions affect the software.
The developers should correct all the errors in the software modules before releasing a new
version.
9. Responsibilities of Test Team Members
Project Manager
●
●
Managing the whole testing process.
Providing all the needed resources for the testing activities.
QA Lead
●
●
●
●
●
Collecting and learning the requirements.
Validation of the documentation.
Planning the testing works.
Monitoring the testing activities, making sure that the works are performed according to
the plan.
Reporting about the progress, number and severity of the found errors.
Test Engineer
●
QA process / logging found errors into the approved bug tracking system.
10. Deliverables
●
●
Test Plan.
Bug reports and reports regarding the testing progress.
​9​
© QATestLab All Rights Reserved