chore(post): add Paris Test Conf 2025 post #473
Conversation
devipilou
force-pushed
the
2025-paris-test-conf
branch
from
fa43c61 to
f438922
Compare
|
This pull request is automatically being deployed by Amplify Hosting (learn more). |
devipilou
force-pushed
the
2025-paris-test-conf
branch
from
1253697 to
b20a8b8
Compare
devipilou
force-pushed
the
2025-paris-test-conf
branch
from
b20a8b8 to
55b2a5b
Compare
| - [Stop the triangles and quadrants, build a real test pyramid](#stop-the-triangles-and-quadrants-build-a-real-test-pyramid-christophe-breheret-girardin) (Christophe Breheret-Girardin) | ||
| - Experience feedback on the creation of a test laboratory - a mix of career change and disability (Solène Lapouge - Aurelia Ribeira) | ||
| - Working with chatGPT & Co: what is the impact on the mental health of testers? (Anne Kramer) | ||
| - [The instability of our tests prevents us from delivering](#the-instability-of-our-tests-prevents-us-from-delivering-sofia-lescano-carroll) (Sofia Lescano Carroll) |
There was a problem hiding this comment.
I was looking at the photos of the slides and seeing one, I was thinking "oh, did they go see Sofia's talk?" 😅
(an ex-colleague of us ^^)
| --- | ||
| For the second time, members of the various QA teams from Bedrock (TVJS, Hypercare, Mobile, BO) were able to attend the Paris Test Conf, a day of conferences on software quality and testing. | ||
|
|
||
| ## Program: |
There was a problem hiding this comment.
I would only list talks this article is about. Else, this is a very long list.
| tags: [conference, testing, quality assurance, Paris Test Conf, 2025, community, event] | ||
| color: rgb(251,87,66) | ||
| --- | ||
| For the second time, members of the various QA teams from Bedrock (TVJS, Hypercare, Mobile, BO) were able to attend the Paris Test Conf, a day of conferences on software quality and testing. |
There was a problem hiding this comment.
This is the sentence / paragraph that's used for the home page. It could be more descriptive?
|
|
||
| Dave Snowden - Knowledge management specialist | ||
|
|
||
| ### Conclusion |
There was a problem hiding this comment.
I read a bit fast and it's a bit blurry in my mind, but I'd live to see something actionable in this conclusion.
|
|
||
| The key difference between __pretotyping__ and __prototyping__ is their purpose and level of development: | ||
| - Pretotyping consists of testing the Idea's Demand (before building) | ||
| - Prototypin consists of testing the Product's Feasibility (after deciding to build) |
There was a problem hiding this comment.
| - Prototypin consists of testing the Product's Feasibility (after deciding to build) | |
| - Prototyping consists of testing the Product's Feasibility (after deciding to build) |
| - UX journey tests (automatable), | ||
| - AB tests (version comparison, distinct from functional tests). | ||
|
|
||
| All teams (PO, QA, developers) are involved in this phase. |
There was a problem hiding this comment.
Same (and same for the other sections below): I'd add a short sentence to describe what each person's role is.
| - They erode the team's confidence in test results, which can lead to ignoring genuine problems. | ||
| - "Flakiness" tends to worsen with "copy-paste" testing practices or the habit of turning a blind eye to random failures. | ||
|
|
||
|  |
There was a problem hiding this comment.
I would crop the photos to remove what's not "the slide" (for this one and a few others)
|  | ||
|
|
||
| ### Why a Post-Mortem? | ||
| Following an incident, the post-mortem goes well beyond simple technical analysis: it aims to understand the root causes, identify collective actions, and continuously improve processes. |
There was a problem hiding this comment.
"collective", or "corrective"?
|
|
||
| #### Animation: | ||
| - Participants are often unhappy, so start with an ice breaker or a round table to de-escalate tensions. | ||
| - Beware of finger pointing: this search for the culprit (Blameless culture) must be eliminated. This does not mean that we will not talk about people's actions. We will talk about everything, but not about a culprit. |
There was a problem hiding this comment.
search for the culprit would not be a blameless culture. I would put the "(blameless culture") part somewhere else in the sentence.
Maybe
Beware of finger pointing: this search for the culprit must be eliminated, and a Blameless culture must be encouraged.
|
|
||
| Paris Test Conf 2025 offered a __varied program__ and __high-quality__ talks. The topics covered, ranging from __automation__ and __security__ to the integration of artificial intelligence, provided a __comprehensive__ overview of the current challenges in software testing. | ||
|
|
||
| Several of the concepts and case studies presented were particularly __relevant__, and we will be looking into applying some of these approaches within our teams in the coming months. |
There was a problem hiding this comment.
Feedback that applies to all taks you summarized: I would love to see more "we have learnt X" or "it's great seeing someone talking about this thing we've started doing recently" or "we are going to change the way we do Z because…"
Add a conf return from Paris Test Conf 2025 by 4 QAs/QALeads.
Publication date will be modified just before merging.