"Testing is the art of looking for all possible combinations of adverse and positive effects on a software"

Seeking to learn more about QA, I searched for LinkedIn courses on QA & Testing. Agile Testing came up tops as a popular course, so I decided to give it a try. While I did learn some interesting concepts, the course focused quite a bit on the Agile ceremony. This will be helpful for folks who’s not yet familiar with Agile or need a refresher.

As I conclude my latest course on Agile Testing with these introductory QA learnings, I’m looking forward to learning more in-depth concepts & tools on QA & Testing.

1. Shift-Left Testing (Instead of Build then Test)
    a. Create Transparency to give feedback earlier
    b. Early integrations for faster feedback
    c. Regular integrations of testing along the way

2. The 3 amigos: (Re)Align different perspectives
    a. Stakeholder
    b. Developer
    c. Tester

3. Questions to ask during Testing (Build Test Plan)
    a. What to test (What is being built)
    b. Where to test (Where are most users using the product)
    c. Which devices to test (Screen size, break point & operating system)

4. Questions to ask during Bug Tracking
    a. Naming convention (Quick identification)
    b. What is the priority (Severity)
    c. What is the matter (What failed)
    d. How did you find the bug (Reproduce)
    e. Where was the bug found (Platform, browser)

5. Manual Testing (Automated testing that’s manually triggered)
    a. Positive Testing (Completion & Correctness)
    b. Negative Testing (Correct handling of invalid input)
    c. Exploratory Testing (Explore & discover)

6. Test Automation
    a. Load Testing
    b. Regression Suite

7. Documentation
    a. Project Plan (How to test the product)
    b. Test Plan (Scope of work, plan of action & testing matrix)

"The bug should serve as a discussion piece in evaluating what degree of quality to uphold"