Activity: How do you test?
(no submission)
Purpose:
- Make (more) friends, get to know others, and think about your study group(s)
- Share opinion / experience related to software testing
- Start thinking about the principles of software testing
You will have ~20 minutes to complete this activity.
To facilitate your conversation, you may want to delegate a timekeeper to ensure you get to all of the tasks.
Tasks:
- Team with your neighbors
(you may team with as many neighbors as your want, but probably not more than 10)
- Get to know your team.
Using the two-breath rule,
introduce yourself, share your name, major(s), the year you are in,
one (or two) interesting thing(s) about you
- You may find something unique about your team, something in common,
or something funny or awesome about your team -- be
creative!
-
Suppose you are testing the following artifacts (we will call them Subject Under Test, SUT).
Work with your team and try to answer the questions.
SUT 1: Expo markers
Your team is tasked to test Expo markers.
Use the provided jumbo post-it and Expo markers.
write down your thought process and/or your tests.
- How should you test?
- How many tests do you need?
- Have you tested enough? How to tell?
- Are your tests good enough? How to tell? — not seeing a problem does not mean there is no problem!!
SUT 2: Compute Project Grade
Consider Compute project grade,
a small web app that takes 6 project scores and computes an average score with or without the lowest score being dropped.
- How should you test?
- How many tests do you need?
- Have you tested enough? How to tell?
- Are your tests good enough? How to tell? — not seeing a problem does not mean there is no problem!!
SUT 3: Google search page
Consider https://www.google.com/search
- How should you test?
- How many tests do you need?
- Have you tested enough? How to tell?
- Are your tests good enough? How to tell? — not seeing a problem does not mean there is no problem!!
-
Be prepared to share ideas / solutions your team discussed to the class
[Optional] Let's try something fun — How about bypass testing Google search page?
Mimic Google search form
Replace GET with POST