Devops for Growth
107.5K views | +0 today
Follow
Devops for Growth
For Product Owners/Product Managers and Scrum Teams: Growth Hacking, Devops, Agile, Lean for IT, Lean Startup, customer centric, software quality...
Curated by Mickael Ruau
Your new post is loading...
Your new post is loading...

Popular Tags

Current selected tag: 'QA - Quality Assurance'. Clear
Scooped by Mickael Ruau
Scoop.it!

Quality Assurance Patterns and Anti-Patterns - DZone - Refcardz

Quality Assurance Patterns and Anti-Patterns - DZone - Refcardz | Devops for Growth | Scoop.it
As software development continues to evolve, the desire to scale efforts across enterprise organizations is growing, resulting in several documented and proficient methodologies for scaling Agile practices to the enterprise. This Refcard will walk through patterns and anti-patterns in quality assurance within the Lean- and Agile forward implementations of one such methodology, the Scaled Agile Framework, also known as SAFe.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

How to Use Test Data for Increased Software Quality

How to Use Test Data for Increased Software Quality | Devops for Growth | Scoop.it
Test data is a major influencer of test reliability and should be the main concern of the people involved in writing the tests.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

'The Real Agile Testing Quadrants' with Michael Bolton

 In this session, Michael Bolton (who has extensive experience as a tester, as a programmer, and as a project manager) explained the role of skilled software testers, and why you might not want to think of testing as "quality assurance".

 

He present ideas about the relationship between management and testers, and about the service that testers really provide: making quality assurance possible by lighting the way of the project.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Types de tests et Les quadrants du test agile –

Types de tests et Les quadrants du test agile – | Devops for Growth | Scoop.it
Ci-dessous, une liste non-exhaustive des types de tests que l'on peut mettre en place sur un projet web. Tous ne sont pas indispensables, mais c'est bien de les avoir en tête pour définir une stratégie de qualité sur un projet. Q1 Les Tests unitaires Ce sont des tests qui vérifient le code en lui-même, morceau…
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Organisation d'une recette

La recette est souvent qualifiée de « projet dans le projet », pour en souligner l'importance de cette phase dans les projets informatiques. Cette page présente les caractéristiques et le déroulement d'un projet de recette fonctionnelle.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Using Jira Sub-Tasks for QA Workflows

Using Jira Sub-Tasks for QA Workflows | Devops for Growth | Scoop.it
If you don’t have an official test management tool, Jira offers enough configurations for both manual and automated testing workflows.
No comment yet.
Scooped by Mickael Ruau
Scoop.it!

Agile Test Strategy Example Template —

Agile Test Strategy Example Template — | Devops for Growth | Scoop.it
Agile Test Strategy Sample Template. What to include in an agile test strategy document? We list the common elements to be included in the test strategy doc
Mickael Ruau's insight:

Preventing Defects

In story workshops, PO, BA, Dev, and QA must be involved.

Scenarios (valid, invalid and edge cases) should be thought of (QA can add huge value here by thinking abstractly about the story) and written down in feature files.

It is important to note that it is the scenarios (more than anything else) that will reveal defects when testing the product, so the more effort and time spent on this activity, the best results at the end.

Because the majority of defects are due to unclear and vague requirements, this activity will also help prevent implementation of incorrect behavior as everyone should have the same understanding of the story.

Likewise, in the sprint planning meetings, the estimates given for a story should include the testing effort as well and not just coding effort. QA (manual and automation) must also be present in the sprint planning meetings to provide an estimate for testing of the story.

No comment yet.
Scooped by Mickael Ruau
Scoop.it!

"Ok Robot, fais les tests"

"Ok Robot, fais les tests" | Devops for Growth | Scoop.it
Tester ses applications web avec RobotFramework
Mickael Ruau's insight:

RobotFramework permet de faire des tests de validation (acceptance testing en anglais).

En général, on utilise Selenium comme moteur d'exécution (mais d'autres outils peuvent également être utilisés), et RobotFramework est simplement une surcouche qui permet de décorréler l'implémentation physique du test ("écrire dans le premier champ puis cliquer sur le 3ème bouton dans le second formulaire") et son sens fonctionnel ("Je m'identifie sur la page d'accueil").

On obtient donc des tests avec une syntaxe très simple proche du langage naturel grâce à l'utilisation de mots-clé (Keywords), par exemple:

Manager can change the user registration fields
Given I'm logged in as a 'Manager'
then I go to Member fields editor
and I add a Text field 'Office name'
and I see the 'Office name' field in registration form 

Ici nous avons créé un test case nommé "Manager can change the user registration fields", et les étapes du test sont des keywords qui sont définis par ailleurs afin de ne pas polluer la lisibilité du test.

La création des keywords est tout aussi simple et utilise la même syntaxe:

I go to Member fields editor
    Go to ${PLONE_URL}/@@overview-controlpanel
    Click link link=Users and Groups
    Click link link=Member fields

On voit qu'on se rapproche un peu plus de la réalité physique du test et on reconnaît ce qu'un outil comme Selenium permet de faire.

No comment yet.