Brian is a Senior QA Engineer with over 15 years of broad experience to draw on as a regular blog contributor for TestLodge. Starting with a Bachelor’s degree in Information Networking and Telecommunications, he has worked on software teams for well-known companies in multiple industries, including Garmin, Commerce Bank, Cox Automotive, and his current employer, CBS Interactive. He has spent time in Taiwan coordinating the testing of an Android handset for Garmin and Asus, and is currently automating testing of multiple websites, developing test plans, identifying and tracking down defect root causes, as part of his testing responsibilities. Brian has also been involved in a mobile app startup developing test processes and is experienced with the automation of website testing.
Setting up a simple but well ordered QA toolbox for your team is a practical way to keep tools and documents together in one place and within easy reach.
Test cases can provide structure within the software testing process, and knowing exactly when to write test cases can save both time, money, and stress.
QA and development teams waste a lot of time, money and effort if requirements don’t have enough acceptance criteria. Read here how to avoid this situation.
It’s a mistake to think that testing needs are the same across all industries and every product. This post shows how all testing circumstances are unique.
In a QA testers work day, it can be hard to know what to prioritize. Some items have higher value than others, so how do we choose and avoid overwhelm?
Many of the QA challenges faced by software testers can be helped by better planning, scheduling and requirements being updated. Learn more about it here.
Software testing takes a lot of time, but how can you take control of your time to finish the work faster? This post can help with better time management.