Guides

Guides is the best source of information if you are interested in the technical details how our engineering team delivers quality software.

Tester Role

The user story status flow diagram can be found here.

Responsibilities

Testers are responsible for:

  • Testing as many use cases as possible.
  • Communicating with the client to clarify requirements of the features.
  • Prepare the necessary data required for testing.
  • Collaborating with the developers and the systems engineer.
  • Reporting bugs.

Building knowledge on application functionality

  • Ask the developer responsible for the feature.
  • Build up the knowledge by testing the requirements described in the user stories.
  • Open the application and explore the functionality.

Workflow

A story is ready for testing only if its status is ‘Developed’. Highest priority is given to the stories at the top of the current sprint.

  • Accept the first story with status ‘Developed’ from the top of the sprint by changing its status to ‘In Testing’ and changing the ‘Assigned To’ to yourself.
  • Analyze the requirements of the ticket.
  • Clarify the requirements with the team members and the client.
  • Prepare a big (diverse) data set which would cover most of the possible cases.
  • Check if the requirements of the ticket are met.
  • Check for edge cases by testing as many of the possible cases using the prepared data set.
  • Create a new story if a bug is unrelated to the ticket currently being tested.
  • If a bug related to the feature was found, return the ticket to the developer by changing its status to ‘Feedback’ and changing its ‘Assigned To’ to the developer. Follow the best practices in chapter Providing feedback when describing the feedback.
  • If the requirements are met and no bugs were found, return the ticket to the developer by changing its status to ‘Tested’ and changing its ‘Assigned To’ to the developer.

Creating a new story

When creating a new story:

  • The Subject should start with the text [Bug].
  • The Subject should be compact and very accurate.
  • A story contains only one bug.
  • Description of the bug should be comprehensive.

Providing feedback

Best practices for describing a bug or a UX issue.

Use screenshots

“A good sketch is better than a long speech”,- Napoleon Bonaparte

Highlight the problem area - it might not be obvious to others what is wrong. We use the Chrome plugin Awesome Screenshot or GIMP on Ubuntu for editing the screenshots. Describe the screenshots in the feedback field of the story.

Ask questions

What happened? Where did it happen? When did it happen? How to re-create the conditions for it to happen? (used to describe complex problems).

Provide credentials

If it is a User specific issue, provide the URL of the page in question and the test account login info.