Please enable JavaScript.
Coggle requires JavaScript to display documents.
SMOKE TESTING (Jira) - Coggle Diagram
SMOKE TESTING (Jira)
BUG TRIAGE:
Bug Triaging:
- When to fix it?
- Is it worth to fix?
- Is it a valid defect?
Backlog:
- Storage.
- Consists of bug, stories, bug reports.
- Consists of number of defects in the system.
Definition:
- Process on what's inside the bug
- Prioritization and Severity
- Team check on if the bug is still an issue
- If your car has a small scratch, it can still drive.
Explanation:
Bug Triage:
- Bug Reports
- Severity and Priority
Bug Test Case:
Severity / Priority:
- You will see a lot of priority.
- You won't see too much severity.
Determining Severity:
- Minor-defects come from code.
- When Key Feature doesn't work, that is priority.
- We don't have severity in Jira
- We only have priority.
Priority:
- Low (can be done once more serious is fixed)
- Medium (normal course of development)
- High (can fix tomorrow)
- Blocker (fix asap)
SMOKE TESTING:
Test Cases:
Example:
- Title (User can log into title)
- Preconditions (user state has priority)
- Steps (example)
- Expected results (No actual result, only in a bug report)
What is it?
- It's a checklist.
- Following instructions will help you test better.
- Test Creation, then Exection
Definition:
- Step by Step instruction on how were going to test an Application feature.
Consists of:
- Layout (mobile or desktop)
- Steps
- Data values
- Expected results
Executing:
- Pass/fail maker
- Comment if failed
- Create a defect automatically in Jira
Why?
- You need the quality of the application with test cases.
- Make sure the computer doesn't burn down.
Test Plan:
- Never build a house without blue prints.
- Biuld a Test plan before testing.
Example:
- Search for a Song
- Play a Song
- Create a New Playlist
- Delete a Playlist
INFO:
Writing Test Cases:
How to write Test Cases:
- Use Zephyr extension
- Describe the initial context
- It is with history of what you've done.
- Test cases are simple
- Keep the steps to 3-5.
- Create test cases for other people.
General:
- Writing Bug reports and Test Cases are different.
Smoke Testing:
- Smoke Testing is to make sure main application functionality, to make sure that it's working.
- Make sure the test makes sure the main functionality of the application is working.
- Used for P1 (critical priority) (P1 is Critical, P0 is Blocker, P2 is bug, etc..)
-
- PURPOSE: Test Case is a car test drive. The purpose of smoke testing is to make sure that main functionality is working.
Smoke Testing:
- Quick test of a Major Functionality (whole application)
Sanity Testing:
- Quick test of a Particular Functionality (feature)
SMOKE SUITE:
DEFINITION:
Smoke Cycle:
- Consists of Test Cases to make a Cycle.
Smoke Test Suite:
- Smoke Test condenses multiple checks into a small suite for pre-staging assessment.
- Developers assess app readiness quickly.
- Combination of MANY TEST CASES.
QUESTIONS:
Logging Tips?
- Never use slashes during titles
- Use pipes when writing titles
- If the bug is a bad user experience, it is listed as High.
- It's okay to shorten your test case, be sure to include important steps.
- During logging, put down your URL browser in description.
- Make mistakes, you're here to learn.
How do I look for a bug again?
- Type = bug AND project = [your project]
INTERVIEW:
Questions?
- What is a bug report?
- What does a Test case consist of?
- What Testing types do you know?
- What is the difference between Smoke and Sanity Testing?