[et_pb_section fb_built=”1″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_row admin_label=”Row” _builder_version=”4.22.0″ _module_preset=”default” background_color=”#fff3cd” custom_margin=”30px||30px||false|false” custom_css_main_element=”overflow:visible” border_radii=”on|0.25rem|0.25rem|0.25rem|0.25rem” border_width_all=”1px” border_color_all=”#dee2e6″ box_shadow_style=”preset3″ box_shadow_vertical=”5px” box_shadow_blur=”15px” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.22.0″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/11\/agile-testing-en.png” title_text=”agile-testing-fr” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][et_pb_blurb title=”Key Points” image=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/10\/key-point.png” alt=”key point” icon_placement=”left” image_icon_width_tablet=”” image_icon_width_phone=”20px” image_icon_width_last_edited=”on|phone” content_max_width_tablet=”” content_max_width_phone=”” content_max_width_last_edited=”on|phone” _builder_version=”4.23.1″ _module_preset=”default” header_font=”Acme||||||||” header_font_size=”22px” background_color=”#edf8ff” image_icon_custom_margin=”1px|0px|0px|0px|false|false” image_icon_custom_padding=”||||false|false” width=”200px” width_tablet=”200px” width_phone=”130px” width_last_edited=”on|desktop” max_width=”200px” max_width_tablet=”200px” max_width_phone=”200px” max_width_last_edited=”on|desktop” module_alignment=”center” height_tablet=”” height_phone=”30px” height_last_edited=”on|phone” custom_margin=”-55px||||false|false” custom_margin_tablet=”-55px||||false|false” custom_margin_phone=”-40px||0px||false|false” custom_margin_last_edited=”on|phone” custom_padding=”5px|5px|0px|5px|false|false” child_filter_saturate=”200%” header_font_size_tablet=”22px” header_font_size_phone=”15px” header_font_size_last_edited=”on|phone” border_radii=”on|0.25rem|0.25rem|0.25rem|0.25rem” border_width_all=”1px” border_color_all=”#dee2e6″ box_shadow_style=”preset3″ box_shadow_horizontal=”6px” box_shadow_vertical=”11px” box_shadow_blur=”8px” text_shadow_style=”preset1″ text_shadow_vertical_length=”0.15em” text_shadow_blur_strength=”0.3em” global_colors_info=”{}”][\/et_pb_blurb][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” custom_padding=”|30px||30px|false|false” global_colors_info=”{}”]<\/p>\n
This article will explore the distinctions<\/strong> between classical<\/strong> and agile<\/strong> testing, examining the concept of continuous testing<\/strong> through Brian Marick’s explanation of the quadrant<\/strong>. We will also discuss the responsibilities of each actor, including those of the quality manager<\/strong>. In conclusion, recommendations<\/strong> will be provided.<\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n The testing approach we present to you has different purposes from traditional methods, which is why we call them agile tests.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.22.0″ _module_preset=”default” background_color=”#e7ffdd” custom_margin=”30px||30px||false|false” custom_css_main_element=”overflow:visible” border_radii=”on|0.25rem|0.25rem|0.25rem|0.25rem” border_width_all=”1px” border_color_all=”#dee2e6″ box_shadow_style=”preset3″ box_shadow_vertical=”5px” box_shadow_blur=”15px” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.22.0″ _module_preset=”default” global_colors_info=”{}”][et_pb_blurb title=”Definition” image=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/10\/active.png” alt=”Prerequisites” icon_placement=”left” content_max_width_tablet=”” content_max_width_phone=”” content_max_width_last_edited=”on|phone” _builder_version=”4.23.1″ _module_preset=”default” header_font=”Acme||||||||” header_font_size=”22px” background_color=”#edf8ff” image_icon_custom_margin=”1px|0px|0px|0px|false|false” image_icon_custom_padding=”||||false|false” width=”200px” width_tablet=”200px” width_phone=”200px” width_last_edited=”on|desktop” max_width=”200px” max_width_tablet=”200px” max_width_phone=”200px” max_width_last_edited=”on|desktop” module_alignment=”center” custom_margin=”-55px||||false|false” custom_margin_tablet=”-55px||||false|false” custom_margin_phone=”-55px||||false|false” custom_margin_last_edited=”on|phone” custom_padding=”5px|5px|0px|5px|false|false” child_filter_saturate=”200%” header_font_size_tablet=”22px” header_font_size_phone=”22px” header_font_size_last_edited=”on|phone” border_radii=”on|0.25rem|0.25rem|0.25rem|0.25rem” border_width_all=”1px” border_color_all=”#dee2e6″ box_shadow_style=”preset3″ box_shadow_horizontal=”6px” box_shadow_vertical=”11px” box_shadow_blur=”8px” text_shadow_style=”preset1″ text_shadow_vertical_length=”0.15em” text_shadow_blur_strength=”0.3em” global_colors_info=”{}”][\/et_pb_blurb][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” custom_padding=”|30px||30px|false|false” global_colors_info=”{}”]<\/p>\n Our<\/strong>definition of agile testing:<\/strong> Agile testing aims to share the responsibilities of testing<\/strong> by automating<\/strong> as much as possible a collaborative specification<\/strong> written in the form of examples<\/strong> in order to deliver a satisfactory product<\/strong> for the development team<\/strong> but especially for our users<\/strong>.<\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text module_class=”pmc-bullet” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n Classic approach <\/strong><\/span><\/p>\n Agile approach <\/strong><\/span><\/p>\n <\/strong><\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row column_structure=”1_2,1_2″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”1_2″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/11\/pyramide1-1.png” title_text=”pyramide1″ align=”center” _builder_version=”4.23.1″ _module_preset=”default” width=”70%” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][et_pb_column type=”1_2″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_image src=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/11\/pyramide2.png” title_text=”pyramide2″ align=”center” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n Our goal is to give maximum visibility on the progress of the product and to be able to refine and\/or evolve the needs of users as quickly as possible.<\/p>\n So we need to have elements Done<\/strong> as quickly as possible, testing is part of our definition of Done<\/strong>.<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” background_color=”#edf8ff” custom_padding=”20px|20px|20px|20px|false|false” border_radii=”on|10px|10px|10px|10px” border_width_all=”1px” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n Testing Strategy and Risk Analysis: Brian Marick’s<\/strong> Quadrants<\/span><\/p>\n<\/blockquote>\n [\/et_pb_text][et_pb_image src=”https:\/\/pmchampions.com\/wp-content\/uploads\/2023\/11\/agile-brian-marick-en.png” title_text=”agile-brian-marick-fr” _builder_version=”4.23.1″ _module_preset=”default” border_radii=”on|10px|10px|10px|10px” box_shadow_style=”preset3″ global_colors_info=”{}”][\/et_pb_image][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text module_class=”blue-list” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n Dial n\u00b01:<\/strong><\/p>\n Dial n\u00b02:<\/strong><\/p>\n Dial n\u00b03:<\/strong><\/p>\n Dial n\u00b04:<\/strong><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text module_class=”blue-list” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n The traditional approach promotes the separation between testing and development activities.<\/p>\n On the contrary, agile methods favor an “extended team” approach<\/p>\n The tester is part of the Dev Team<\/p>\n Sharing of responsibility involves two conditions:<\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\n The activities of the tester change with the changes that IT undergoes and initiates.<\/p>\n We need specific skills around testing: the role of <\/span>Quality Analyst<\/span><\/p>\n [\/et_pb_text][\/et_pb_column][\/et_pb_row][et_pb_row _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_column type=”4_4″ _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”][et_pb_text module_class=”star-list” _builder_version=”4.23.1″ _module_preset=”default” global_colors_info=”{}”]<\/p>\nWHY AN AGILE TESTING PRACTICE<\/h2>\n
HOW TO SET UP AGILE TESTING<\/span><\/h2>\n
THE NEW CHALLENGES OF SOFTWARE TESTING: TOWARDS A NEW WORLD
<\/span><\/h3>\n\n
\n
<\/span><\/li>\n<\/ul>\nCLASSIC TESTING PYRAMID VS AGILE TESTING PYRAMID <\/h3>\n
CONTINUOUS TESTING<\/h3>\n
<\/ul>\n
\n
\n
\n
\n
\n
\n
TESTING, A SHARED RESPONSIBILITY<\/h3>\n
\n
DO WE STILL NEED THE TESTERS?<\/h3>\n
RECOMMENDATIONS<\/h2>\n