The test plan is very important in any organization. The Test Plan defines the project’s objectives, scope, approach, and focus of its testing efforts. The process of preparing a Test Plan provides an effective way to think through the efforts needed to validate the acceptability of the application under test (AUT).
Words From a Purple Mind
Input on the important topics …to me of course
Automation Testing
The Ultimate Roundup of Software Testing Magazines
Software testing has expanded over the years, there are more and more magazines being published. Here is a roundup of magazines that focus on software testing.
Quality Assurance Roles and Responsibilities
There are various roles on projects, some people may play more than one role. You should always check with your organizations testing methodology on what your role(s) are. Below is a breakdown of quality assurance roles and responsibilities:
Phase: All
-
Test Lead
- Oversees all testing staff and activities for all assigned applications
LondonTester Is Helping Software Testing Professionals Find Jobs
I previously wrote a post on sites that can help you find your next QA job. In that post I listed a newcomer site called LondonTester. The site is now live.
20+ Sites To Help You Find Your Next QA Job
Are you looking for a new position or a new contract? Below is a list of some great sites for you to check out to find your next quality assurance job/contract.
I also created the Twitter List “@jayphilips/employment” so you can get updates from all of the people listed on this post that have a Twitter account with one just click.
20+ Sections That Should Be In Your Testing Strategy
The Test Strategy defines the general approach that will be employed to test the software and to evaluate the results of testing. It outlines the testing approach, identifies the required resources and communication plan and lists the deliverable elements of the project.
This Test Strategy also supports the following specific objectives:
15+ Sections That Should Be In A Testing Methodology
The testing methodology is very important in any organization. This document lays the foundation for the testing group. It’s main purpose is to set consistency and discipline to the testing process. It guides you through the process by defining why testing is being done, who is testing, what is produced during the various phases, and when it testing should be included in a project.
What types of documents are needed for software testing?
Software testing is not just limited to testing the application, it also includes documentation. Testing documentation is used for a variety of reasons:
- Explains the purpose & goal of testing
- Explains will be tested & how
- Provide testing results to the project team
200+ Software Testing Blogs and Tweeters
This is a extension of the blog post “10+ Software Testing Blogs“. This blog post has 200+ software testing blogs and tweeters.
I also created the Twitter List “@jayphilips/software-testing” so you can follow all of the people listed on this post with one just click.
- Abby Fichtner
30+ Common Testing Mistakes
I was cleaning out a folder on my machine when I stumbled on an oldie but goodie PDF called “Classic Testing Mistakes” by Brian Marick.
In the paper he states how he breaks the classic mistakes into 5 themes and how to resolve the mistakes: