How do you handle feedback and criticism from developers or managers who prefer scripted testing?
由人工智能和领英社区提供技术支持
在这篇协作文章中查找专家回答
由社区从 3 条内容中精选。了解更多
The first step to handle feedback and criticism is to understand where it is coming from. Developers or managers who prefer scripted testing may have different goals, expectations, or constraints than you. They may want to have more control, traceability, or repeatability of the testing process. They may also have to comply with certain standards, regulations, or contracts that require scripted testing. Try to empathize with their perspective and acknowledge their concerns. This can help you avoid conflicts and build rapport.
The next step is to explain your approach and the benefits of exploratory testing. You can use examples, stories, or evidence to show how exploratory testing can help you find important bugs, improve test coverage, and collaborate with other testers and developers. You can also highlight how exploratory testing can complement scripted testing, rather than replace it. For instance, you can use exploratory testing to discover new risks, generate new test ideas, or verify fixes, while using scripted testing to check known requirements, cover regression, or automate tasks. You can also use tools or techniques to document, report, or measure your exploratory testing activities, such as session-based testing, mind maps, test notes, or metrics.
The third step is to seek feedback and improvement from developers or managers who prefer scripted testing. You can ask them for their opinions, suggestions, or questions about your exploratory testing approach. You can also invite them to observe, participate, or review your exploratory testing sessions. This can help you learn from their expertise, improve your skills, and demonstrate your value. You can also use feedback and criticism as an opportunity to challenge your assumptions, test your hypotheses, or refine your strategies.
The fourth step is to respect their preferences and boundaries. You may not always be able to convince developers or managers who prefer scripted testing to embrace exploratory testing. They may have valid reasons, preferences, or constraints that prevent them from adopting or supporting exploratory testing. In such cases, you should respect their choices and work within their expectations. You can also look for ways to compromise, collaborate, or integrate your exploratory testing approach with their scripted testing approach. For example, you can use scripted testing as a starting point, guide, or check for your exploratory testing, or vice versa.
The fifth step is to find allies and mentors who can support your exploratory testing approach. You can look for other testers, developers, or managers who share your passion, vision, or goals for exploratory testing. You can also seek mentors who have more experience, knowledge, or influence in exploratory testing. You can learn from them, exchange ideas, or seek advice. You can also join communities, networks, or groups that promote exploratory testing. You can find resources, events, or opportunities to grow your skills and network.
The final step is to keep learning and experimenting with exploratory testing. You can always improve your skills, knowledge, or methods in exploratory testing. You can also explore new tools, technologies, or domains that can enhance your exploratory testing capabilities. You can also try new challenges, experiments, or projects that can stretch your limits and spark your creativity. By keeping learning and experimenting, you can stay curious, motivated, and confident in your exploratory testing approach.
更多相关阅读内容
-
Exploratory TestingHow do you train and coach your team on exploratory testing skills and techniques?
-
Software TestingYour team is divided on exploratory testing. How can you navigate conflicting opinions effectively?
-
Functional TestingHow do you balance exploratory testing with scripted testing in your test strategy and plan?
-
Exploratory TestingHow do you define a test charter for exploratory testing?