Here's how you can enhance your Quality Assurance skills by learning about different testing methodologies.

Manual Testing is widely used because automated tests are expensive. It requires attention and plays the role of the end user. For manual tests, it is necessary to have a keen eye, especially for details. For this, creating a mind map with scenarios greatly contributes to an excellent result. Manual testing involves the intuitive exploration of the software to identify flaws that, most of the time, automated tests do not detect. Practice is fundamental, so getting involved with real projects, whether personal or professional, provides a practical view of how to apply different testing methodologies. What is more, continuous feedback helps in improving QA skills.

Another important driver for manual testing is when automated tests are too expensive (for example in complex mechatronic products at system level) or when time pressure does not allow creation of test automation. The latter is rather tricky though as typically such environments end up in a circle, so always be careful if this is the default answer.

By minimizing the manual effort where possible using automation testing we can actually utilise that time to learn and implement test strategies that are more useful.

One important aspect of automated testing is not yet mentioned; ensure testing at the right level using stubs and drivers. Too often I encounter "unit tests" where the whole system is included in the test making the test way too slow, complex and difficult to analyse a failing test case.

Automated testing is an important skill to have. You can cut down on testing time by having skill in automation testing. In situations where the manual testing team and automated testing teams are separated , the manual tester could reviews the automation scripts so it aligns with what is required.

Performance and security are only 2 of the quality characteristics of ISO 25010. Instead of picking "randomly" these 2, have a business level conversation on which of those characteristics matter the most and develop tests to address those concerns.

Security testing involves evaluating the security measures of software systems to identify vulnerabilities and ensure they are robust against potential threats. It includes conducting tests to uncover weaknesses in applications, networks, or systems that could be exploited by attackers. Security testing aims to protect sensitive data, prevent unauthorized access, maintain the integrity and availability of software. Techniques used in security testing may include penetration testing, vulnerability assessments, ethical hacking, and risk assessments. By performing thorough security testing, organizations can proactively identify and mitigate security risks, ensuring that their software applications are secure & resilient against cyber threats.

Mobile testing can be tricky, as you have to keep in mind how your device works, which can differ from make, model, and operating system. It is always advised to test on multiple devices. To determine which specifications these devices should have, gather data about your target users or obtain a range of devices that covers the most common use cases. Learning error-guessing techniques is crucial, along with understanding how mobile devices operate, such as how applications behave in the background and how data is cached. Additionally, consider how accessories might interact with the device and what issues they might cause. All in all, error-guessing can prove to be your best ally here.

Fail fast, fail often! A solid CI cycle is key. Adding unit tests to these cycles that are utterly fast (which a proper unit test is) builds confidence rapidly that the build is not broken by a change. static code checking tools like TiCS give insight if the code quality improved or not by the change.