Test management knowledge? That said, there are a variety of approaches to software testing, all of which are equally important in reaching a realistic conclusion to the pressing questions facing developers and testers: Does the application as a whole work? Do all features function as expected? Can the application withstand the demands of a heavy load? Are there security vulnerabilities that could put users at risk? Is the application reasonably easy to use, or will users find it a pain in the a$$?
There are a lot of great staff out there and typically with testers I find attitude is everything! Sure, you can learn great technical skills but if your team members don’t have the right attitude or intuition for testing you will probably be out of luck. If you are lucky enough to have great Test Leads or Testers you will probably find they have the right attitude and social skills to deal diplomatically with people of all levels in all sorts of roles. JDI is always a good approach! Speaking of tester’s intuition, check out one of the earlier blogs in the series on using your intuition, Testing and Bad Smells: When to Investigate Potential Bugs. Thanks Penny for a great post!
If you’d like to step up your skills from the software testing basics, and access some of the best insider knowledge in the industry, this ebook is for you. A Test Manager’s Guide will make an essential addition to your collection as you continue to develop within this field. After passing the ISTQB Foundation Certification, this eBook was great source to better understand what to expect from the Test Managers working on my Software Projects. Explore a few extra info at Test Analysis.
Find your good enough threshold. Everyone wants perfect software, but budget constraints, business priorities, and resource capacity often make ‘perfect’ an impossible goal. But if perfection isn’t your goal, what is? Recognize that the goal of testing is to mitigate risk, not necessarily eliminate it. Your applications don’t need to be perfect — but they do need to support your business processes in time to leverage new opportunities without exposing companies to unnecessary or untenable risk. Therefore, your definition of quality may vary by application. As you initiate a project, get the right roles involved to ask the right questions: What constitutes perfect versus good enough versus unacceptable?
Quarantine software testing trick of the day : As you are developing and testing, team members need to make sure they are capturing everything more religiously than they might do if working in the office. For a tester, they could normally just show someone else (e.g. a developer) what happened on their screen, but when you are Teletesting, that is harder to. Use screen capture tools (like a free google extension – SpiraCapture) to capture what you are doing and then save the results into a tool like SpiraTest so that you have a record of what you just did. Similarly, make sure you document any changes or questions about requirements as a comment in the requirement. If you are not sure what the requirement means, add a question as the comment. If you are worried you will forget to clarify, just add a task to the requirement so that it is not forgotten. Teams should err on the side of adding tasks as well as comments to make sure things are not lost. Also as mentioned in item 3. if you need to get clarity on something, it’s fine to use IM tools, but make sure the results from that discussion make it into the tool being used for the source of truth. See more details at cania-consulting.com.