Pages

Software testing book for preparing testing interviews and learning basics of software testing [download]


I am in process to compile a list of good books on software testing. Soon I will share this list with you. But lately I am getting too many requests to share any book on software testing for preparing software testing interviews. So here is a quick post to share an online testing book I found “A Software Testing Primer” by Nick Jenkins.
Basically this book is an introduction to software testing. So those who are new to software testing field can start their preparation by reading this book. You will get basic idea of manual and automation testing.
Here is a summary of what this book is covering:
  • What is the need of software testing?
  • Different software development models
  • Testing in the software development life cycle
  • How to develop testing mindset?
  • Regression Vs. Retesting
  • White box Vs. Black box testing
  • Verification and validation
  • Alpha and beta testing
  • Unit, Integration and System testing
  • Acceptance testing
  • Automation testing – Basics
  • Testing the design
  • Usability testing
  • Performance testing
  • Test planning
  • Test estimation
  • Test cases and elements of test cases
  • Test tracking, Test planning and Test plan review
  • How to manage defects and defect reports?
  • Test metrics for testers
  • Product release control
In all this book is a nice introduction to software testing. Author explained some key software testing concepts like Regression and Retesting difference, Alpha and beta testing etc. where many testers get confused.
Download “Testing Primer” book:
To download this book Click here
What is your favorite software testing book? Also share your ‘best software testing book’ experience with our readers.

 
 

10 Tips to Help You Achieve Your Software Testing Documentation Goal



Here are the top 10 tips to help you achieve your software testing documentation goal:
1. QA should involve at the very first phase of project so that QA and Documentation work hand in hand.
2. Process defined by QA should follow by technical people, this helps remove most of the defects at very initial stage.
3. Only creating and maintaining software testing templates is not enough, force people to use them.
4. Don’t only create and leave document, Update as and when required.
5. Change requirement is important phase of project don’t forget to add them in the list.
6. Use version controlling for everything. This will help you manage and track your documents easily.
7. Make defect remediation process easier by documenting all defects. Make sure to include clear description of defect, reproduce steps, affected area and details about author while documenting any defect.
8. Try to document what is required for you to understand your work and what you will need to produce to your stakeholders whenever required.
9. Use standard template for documentation. Like any excel sheet template or doc file template and stick to it for all your document needs.
10. Share all project related documents at single location, accessible to every team member for reference as well to update whenever required.
I am not saying that by applying above steps you will get sudden results. I know this change won’t happen in a day or two, but at least we can start so that these changes start happening slowly.
After all “the documentation needs documentation”.  Isn’t it?
Share your tips. How you maintain software testing documents related to your project?