• Selling Bugs for Software Testers Course

  An Experiment I would like to see if there is demand for me to provide a course on improving persuasion skills for software testers. If someone purchases the course I will produce it and attempt to deliver the content as soon as possible. Check out the promo video on the linked page. The Curriculum The preliminary curriculum is listed below. If anyone decides to purchase the course I would love to receive any feedback on what could be improved. If there is a topic that has not been covered I would be more than willing to attempt to include it in the future. Interest in Python or .NET programming could be options in the future as well. The Overarching Goal, Why does selling bugs matter? Why does this matter? Is this a bug? Where does this bug fit in relation to everything else? The QA Engineer Role Provide Information and constructive feedback Tactical Empathy, Understand the roles you are communicating with Developers Product Owners Executives Combination of Developer and Product Owner Software Architect Tools for being persuasive Advanced Listening Mirroring and Labels Calibrated Questions Face to Face versus Email or Chat Meetings Accusation Audit Tone Persuasive Work Products Test Strategy Storytelling Mindmaps / Concept Maps Metrics and Visualizations Bringing it all together Unifying the techniques and applying them

  19.05.2019 | 5:30 קרא עוד...

• Measuring performance based on bugs found

    Bug reporting and performance measurement Appraisal season So it's time for reviews and we're looking back into the last 6 months of what's happened and reviewing them. First and foremost it's a measurement of the performance of the employees to make sure of the following things: Working to the required standard Address key areas ... [Read more...] The post Measuring performance based on bugs found appeared first on The Life Of One Man.

  19.05.2019 | 2:18 קרא עוד...

• Applications are more than just code

  By Matt Long I was at TestBash Brighton recently, and a common theme kept coming up: “You can be technical without knowing how to code!” Richard Bradshaw, TestBash organiser, even did a 99 second talk on the topic. He listed various skills – git, debugging, changing the microwave clock. If you have these skills as a tester, there are plenty of uses for these skills. If you have an agile or DevOps culture – where roles are less set in stone, and teams swarm on problems – you’ll get loads of opportunities to use them. Well, apart from the microwave clock. Learning the ecosystem It’s important to realise most developer skills aren’t coding. If you’ve tried to learn coding, you’ll know lots of other skills can get in the way. You start writing a simple application and lots of good practice pops up. Your developer friend says you should set up a git repository. Then instead of installing dependencies manually, it’s better to set up a dependency manager. Then you learn how to compile and run the code. The list goes on. This can be very daunting, and quickly turns into yak-shaving. This seemingly never ending list of things to learn doesn’t stop with a developer’s skillset. Run a production-grade environment, and SRE/Ops skills will get in the way. Ops ensure that users can use your environments. They do all kinds of things. Backups. User and authentication control. Familiarity with the Linux CLI to debug issues. Log monitoring and analysis.[…]

  19.05.2019 | 10:54 קרא עוד...

לרשימה המלאה >>