FAQs Archive - Page 5 of 6

Q: How can I become a Digivante tester?

[fusion_builder_container type="flex" hundred_percent="no" equal_height_columns="no" hide_on_mobile="small-visibility,medium-visibility,large-visibility" background_position="center center" background_repeat="no-repeat" fade="no" background_parallax="none" parallax_speed="0.3" video_aspect_ratio="16:9" video_loop="yes" video_mute="yes" border_style="solid"][fusion_builder_row][fusion_builder_column type="1_1" layout="1_1" background_position="left top" background_color="" border_color="" border_style="solid" border_position="all" spacing="yes" background_image="" background_repeat="no-repeat" padding_top="" padding_right="" padding_bottom="" padding_left="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="small-visibility,medium-visibility,large-visibility" center_content="no" last="true" min_height="" hover_type="none" link="" border_sizes_top="" border_sizes_bottom="" border_sizes_left="" border_sizes_right="" first="true"][fusion_text] Visit our Become a tester page to find out everything you need to know [/fusion_text][/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]

Q: Is automation suitable for centre or shift right testing related to weekly or monthly releases?

No. We think automation brings benefits specifically in unit testing, integration and where continuous improvement/ continuous development (CI/CD) is used.

Q: How do I prevent automation test environment deterioration?

We recommend only automating stable areas that are easy to maintain.

Q: Should I focus my resources purely on automating?

Automation is just one weapon in the QA armory. We recommend a nuanced approach: supplement automated testing with other QA approaches including planning, manual and crowd testing, user and accessibility testing. We recommend looking at the whole, not just focusing on automation alone.

Q: Should I automate everything?

No. Only automate stable entities with repeatable actions. Choose cases where there isn’t much change, to avoid higher maintenance costs and gaps in automation coverage.

Q: Should I keep my automation resources separate from the rest of QA?

No. We recommend fully integrating them with the whole QA team. Ideally, use the same team for automation and crowd testing, so they’re governed by one QA process.