Manual testing workflow



  • As our app is becoming more mature and we are hiring some extra hands, we have decided to introduce some manual testing before things get into production.

    The problem: we never did this before. Or rather, I have never done this before.

    I started with a simple markdown document, just to get me going. Here's what I was thinking.

    Testing flow

    General instructions
    • Perform steps in the order specified below
    • If something is expected or "should", check to see if it is actually the case
    • If you get an error or something doesn't work per spec,
      • Take a screenshot
      • Write a short simple note of what you think wen't wrong (if feasible)
      • Send it to your manager. They will organize how / in what format
    Layout
    1. Log in as test / test
    2. Click the reload button in the top-right. Expected behavior: the current page should reload.
      ....
    Profile
    1. Click the user drop down in the top right, then click "Account"
    2. Profile tab should display data about user account. User: test. Role: test.
    3. Go to Security tab.
    4. Under old password enter "test"
    5. Under new password enter "test"
    6. Under repeat password enter "test"
    7. Click "Change password"
    8. You should be logged out. There should be green message at the top, saying you have changed the password.
    9. Login as test / test

    Then I decided to switch to google doc, because that is something managers will actually be able to maintain.

    Then I decided to make a google form, so the testers might be able to check each of these items.

    I am not sure this will work out, though. Can I create a new form each time we need to test an update, based on the same template?

    That is when I decided to come here 🙂

    My goals for this testing workflow:

    • Create this in a format that non-technical people can update (so they don't have to bother me)
    • Make it simple for testers to go through. Ideally, they would have a way to track how far they've come (eg checkboxes for each step). Maybe even have a way to attach found defects within the same form
    • It doesn't have to be too elaborate for now. We just need something to get us started, we can make it more elaborate with time
    • Zero budget (meaning free googly spying shit or open source)
    • Most importantly, something I don't have to invest a whole lot of time into setting up and maintaining

    Any advises for a testing newbie? How are you doing this?

    I'll keep going with google forms until told I am an idiot and shown something better.


  • I survived the hour long Uno hand

    @cartman82 said in Manual testing workflow:

    Then I decided to make a google form, so the testers might be able to check each of these items.

    This is one of those things that sounds like a good idea, but I'm not sure it's not overkill. I tend to use checkboxes as a bullet point and print it out to hand to people. It lets them keep the app on their monitor instead of switching back and forth. (Not relevant if your testers get two monitors, but we tend to use contractors and give them the shittiest equipment known to man).

    I would include:

    • How to take a screenshot. Do you have software you want them to use, or just printScreen?
    • You're testing web, right? Defect reports need to include browser and version as well as OS and version. Eventually you'll probably do cross-browser verification, right? Everyone seems to want that pretty fast. A report can come in via email, but if you have to hunt down the relevant details, it'll waste everyone's time.


  • @Yamikuronue said in Manual testing workflow:

    This is one of those things that sounds like a good idea, but I'm not sure it's not overkill. I tend to use checkboxes as a bullet point and print it out to hand to people. It lets them keep the app on their monitor instead of switching back and forth. (Not relevant if your testers get two monitors, but we tend to use contractors and give them the shittiest equipment known to man).

    Good idea. An actual physical piece of paper never even occurred to me. 🙂

    Do we even have a printer in the office? Hmm...

    How to take a screenshot. Do you have software you want them to use, or just printScreen?

    I expect these guys to be able to take a screenshot. If not, managers can take care of that.

    You're testing web, right? Defect reports need to include browser and version as well as OS and version. Eventually you'll probably do cross-browser verification, right? Everyone seems to want that pretty fast. A report can come in via email, but if you have to hunt down the relevant details, it'll waste everyone's time.

    Yeah, they are already doing 4 different browsers. Managers will take care of browser version, when they pass it along to me or create a ticket.


Log in to reply
 

Looks like your connection to What the Daily WTF? was lost, please wait while we try to reconnect.