The role of the software tester (QA): guaranteeing quality before publication
- Reworking software means taking over existing code to correct it and make it evolve.
- We start by accessing the code, then carry out a free maintainability analysis.
- Depending on the quality of the code, improvements are made using the same technology or part of the code (often the back-end) is overhauled.
- Changing service providers allows you to unlock fixes when the current team is no longer available.
- Updating a language or migrating a technology improves performance and security.
Le role of software tester (QA), In an IT team, the work really starts when the functionalities have been developed: it is often the person who “gets the hot potato”, because he is the one who has to make the decisions. last person to see the application before it is published with users.
Its objective is simple to formulate, but demanding to execute: to ensure that what comes out is correct, It meets expectations and is ready to be used under the right conditions.
Why the tester is “the last barrier” before the users
In the video, the central point is responsibility: the tester intervenes just before the product is made available. This implies a requirement for rigour high, because after him it's the users who discover the problems.
In practice, this “last link” position makes QA a direct lever on the perceived reliability of the product, and on the post-release support load.
Thinking like a user: 80% / 20% logic and borderline cases
The tester needs to keep a constant eye on how a user is going to use the application:
- 80% users will follow “classic” usage,
- but it must also identify 20% of behaviour (atypical use, errors, unexpected paths).
This ability to “step outside the ideal scenario” is what allows bugs and inconsistencies to be found before publication.
Testing misuse: defining and validating expected behaviours
The video gives a concrete example: a field where a price. Testers must ask themselves:
- Can this price be negative?
If the expected answer is “no”, then it must test the case:
- enter -200 in the field,
- and check the behaviour expected (example given: the number is automatically reset to zero after encoding).
The idea is to understand how a user can misuse the platform, then validate that the application reacts as expected.
Lighting (general): this approach requires business rules (“authorised / prohibited”) to be made explicit and checks to be made that the interface and application logic actually apply them.
Involve QA before development to avoid costly returns
A very operational point in the transcript: it is “very interesting” that the tester is present during feature presentations, even before for development to begin.
Why is this?
- Because of their experience of the behaviours observed during testing, they can alert the functional analyst and the Product Owner: “Careful, have you planned for this?”
- This means incorporating exceptional cases that need to be treated.
The benefit put forward: avoiding the need for round-trips with developers, which is often the case expensive on a project.
The tester in an agile / Scrum team: backlog, PO, analyst, developers
The tester is part of a team agile / Scrum with its own role, alongside the Product Owner, the analyst and the developers. Their aim is to “make their contribution” by checking that :
- developments are correct,
- they follow the specifications, also known here as backlog,
- and that the product is brought to market in good condition, function after function.
Key qualities: rigour, patience and repetition of tests
The transcript cites two major qualities:
- the patience, because functional testing takes time,
- the ability to detail and test several variations of the same behaviour.
In practical terms, testers can pass minutes or hours on the same functionality, until we are sure that the behaviours have been dealt with.
To remember
- The QA tester is the last stage before publication: rigour is essential.
- It is designed for “standard” use (80%) and atypical cases (20%).
- It also tests the improper use and checks the expected behaviours.
- Example: price field → test a negative value and the expected reaction.
- Involving him before development helps to anticipate borderline cases from the outset.
- In agile/Scrum, it validates compliance with the backlog/specifications.
- Patience is key: repeat and vary the tests until all the scenarios are covered.
The next stage
If you want to ensure quality before going live (QA, tests, agile organisation around validations), you can :
- book a appointment with a QA expert
- or contact us directly via QA and test projects form
- Ensure the quality of your applications with a QA approach complete
Tell us about your project
One exchange, a thousand possibilities.
Describe your vision to us using this form: we'll analyse your request and get back to you within 24 hours with personalised advice and a concrete action plan.
We have the team and the resources to help you with your projects. Give us the details in this form and we'll get back to you as soon as possible to discuss them together.
Checks that the application is correct before it is published to users. It also anticipates cases where users might misuse the platform and validates expected behaviour. It is there to frame an approach QA testing for application development
It tests the “classic” path used by the majority, then explores atypical behaviour. The example given is a “price” field: ask yourself whether a negative value is possible and check the expected reaction of the application.
Look for an ability to think in terms of “use + exceptions”, to formalise expected behaviour, and to collaborate with the PO/analyst/developers from the very start of feature presentations. If you need QA or technical support, please contact us. QA or Test Automation support contact us via QA project form.
Yes, by integrating a tester into the agile flow to validate what comes out against the backlog as it goes along, rather than waiting until the end. The easiest way is to talk about it in a project slot, make an appointment with a QA expert in Belgium.
Reintroduce structured QA validation for each feature, including testing for atypical cases and misuse. Involving the tester as soon as the functionality is presented reduces costly feedback and surprises. Contact the QA and web application testing team .