SQA Online Program
Lessons Plan:
- Introduction: Software QA Profession, curriculum, setting expectations
- GUI (Graphic User Interface) and Usability Testing
- Mastering GUI Bug reports
- Bug Reporting and Bug Tracking
- Energy-Telecom reqs and functionality testing
- Test case – structure and basic points
- Mastering Test cases
- Test Documentation – test case, test suite, test plan
- Software Development Life Cycle – Agile, Scrum, Waterfall
- Introduction to Automated Testing
- Test documentation and bug reporting Practicum-1
- Test documentation and bug reporting Practicum-2
- Interview questions related to Software Quality Assurance
- Interview questions related to Types of Software Testing-1
- Interview questions related to Types of Software Testing-2
- Job market. Job search as a process.
- Job Search: Keyword coding of profiles
- Networking. Talking to recruiters.
- Common interview questions. Company/Project story.
- Working with Craigslist, Meetup. Answering student questions.
Resources:
GUI Standards for Windows 7/Vista Windows XP/2000
Usability standards for Web Applications book_pdf
Comparison of issue-tracking systems
Session 1. Introduction April 4, 2019 November 11, 2019 March 3, 2020
Home Work Assignment:
- Watch Session 1 pre-recorded webinar (Youtube video) PPT
- Learn Interview Questions and Answers-1
- Take survey on the SQA Basics-1
- Watch James Bach video
Interview questions covered in the session:
- What is Quality?
- What is Software Quality?
- What is Software Quality Assurance?
- What is the difference between Software Testing and Software QA?
- What is Software Testing?
- Is it possible to find/fix all the bugs in a software product before it goes to the customers?
- Then – Why test?
- What is black/white box testing?
- Describe a bug?
- What is use case?
- What is the most important impact QA can have on a product development process?
- What is Negative testing? Positive?
- Which type of testing results in highest number of bugs found?
- What is the software development life cycle?
Session 2. GUI/Usability Testing August 5, 2019 November 12, 2019 March 5, 2020
Home Work Assignment:
- Watch Session 2 pre-recorded webinar (Youtube video) PPT
- Familiarize yourself with the www.usability.gov web site
- Apply GUI checklist to the Energy-Telecom Online Form
- Repeat Interview Questions and Answers-1
- Take survey on the SQA Basics-2
- Watch What to do with today? video on Youtube
- Create an account with www.utest.com follow the guidelines
- Register at www.forum.portnov.com
- GUI test assignment
Interview questions covered in the session:
- What is software usability?
- What is usability testing?
- What is GUI testing?
- Where the GUI standards are coming from?
- What are the typical GUI problems you look for on a web page
- Tell me more about WEB Usability Guidelines published by US Government
Session 3. Mastering GUI Bug reports – style/vocabulary August 8 November 14 March 9
Home Work Assignment:
- Watch the Pre-recorded webinar for Session 3
- Write at least 10 bug reports on Taulia and/or Energy-Telecom applications
- Repeat Interview Questions and Answers-1
- Watch Zig Ziglar Attitude Makes All The Difference video on Youtube
Bug Reporting Rules:
- Do not assume all the companies have same approach to writing bug reports
- Rule of WWW – What happened, Where it happened, under Which circumstances
- “Problem” bug report versus “Solution” bug report
- Bug report is not about perfect English
- Before reporting a bug, make sure that you are using the latest version of the AUT
- Report a bug immediately, do not postpone
- Make sure the bug is reproducible before reporting
- Minimize number of steps-to-reproduce
- Write one bug report for each fix to be verified
- The difference between actual and expected results should be clear
- Do not quote the violated rules or requirements (developers know them) – just talk about the problem itself
- Do not assume developer knows less than you do about the application
- Bug reports should be as concise as possible
- Bug report should be as complete as possible
- Attach screen shots, data files, logs to clarify the bug description
- Each “problem” has a story (each decision is a compromise) research before reporting
- Use technical terms, not “people off the street” language