SWTC Manchester - Questions From Our AMA

🗄️ Archive
1

Thank you all for attending the final session from SWTC Manchester 2018. I hope you enjoyed the meetup and thanks to all that contributed questions and answers this evening. Also a huge thanks to Equal Experts for hosting us.

Here are the questions that were asked tonight, please feel free to post answers to any of them. Probably best to quote the question you are answering. Or perhaps they will trigger a few blogpost ideas, if so, share them here so we can all read them.

  • In 2019, is the ISQTB still seen as relevant to have?
  • What’s the best way to learn more about Security Testing?
  • How can I get/find my first job in testing?
  • What programming languages are in demand for automation?
  • What skill is the most in demand, automation of manual?
  • What makes a great software developer in test?
  • What is dev testing?
  • For a tester to develop + progress in their careers, do they have to change companies?
  • What is the 3 amigos?
  • How can testers use Product Owners and Business Analysts to their advantages?
  • Bosses want 100% automation, but does that put quality at risk, how do we solve this?
  • Any 2019 testing trends we should be aware of?
  • What do you enjoy and dislike most about testing?
  • What other automation can we do aside from UI, API and unit?
  • Best place to start with automation?
  • How do we get rid of last minute UAT change requests?
  • Should automation be started by testers or developers?
  • What are some good testing metrics?
  • How to foster an effective relationship with developers?
  • How to correctly nurture graduate dev curiosity?
  • How to grow in a greenfield test environment?
  • Is there a way to get practical sdoftware testing experience without being in a role?
2

How do we get rid of last minute UAT change requests?
I actually think we should be embrace them in order to get rid of them but we should be realistic in regards to setting expectations when it comes to delivery.

Last minute UAT change requests usually comes with stakeholders simultaneously expecting delivery on the same date originally agreed. Never commit to a change without consulting the entire team but be open to the fact that delivering it could be possible.

Talk to the team members and try and understand the scope of the change. Return to the stakeholder with a proposal for doing said work and adjusted timelines accordingly.

This, (in my opinion) provides the best of both worlds as the customer still gets the chance to see the change they want but at a cost. It might also make them think twice about requesting things so late in the game in future

3

In my opinion, it can be any of the programming languages like JAVA/Python/C#/JS/RUST etc…Concentrate on 1 /few languages and get mastered that helps to gain expertise.

Language selection can depend on multiple factors like:
a) Automation Tool that is planned to use
b) Language used by your dev team to develop the application etc

4

I like finding design level defects, or giving more user stories to dev team which weren’t thought through by them :slight_smile: . Quality Engineers who are even freshers generally will have an overall idea of any application that is under test which usually not the case with developers or others. Testing gives a holistic view .

Do not like when devs reject the idea/defect saying technically not feasible. In the AI/ML era , are there still any limits of not being able to implement tiny changes