Entries Tagged 'Basics of Software testing' ↓
June 2nd, 2013 — Basics of Software testing, Questions & answers, Testing Interview questions
We have done ISTQB online tests previously. Now here is an attempt to test your software testing basic knowledge with a simple 20 question test. The following software testing mock test is designed to test your ability to meet software testing requirements.
This free online software testing quiz will help you for self assessment and prepare for other certification exams as well as software testing interview.
This is just the first of many more tests to come. We will be covering similar Continue reading →
January 26th, 2012 — Basics of Software testing, Manual Testing, Software Testing Books, Software Testing Templates, Testing Interview questions
I am glad to share “Manual Testing Help” eBook prepared by one of our readers. The content of this eBook is very useful to understand manual testing concepts, testing methodologies and preparing for software testing interviews.
Here are some of the topics covered in this book:
- Fundamentals of software testing
- When defects gets introduced in SDLC?
- Why does software have defects?
- What is Verification?
- What is Validation?
- Software Testing Techniques
- Continue reading →
August 15th, 2011 — Basics of Software testing, Testing best practices, Testing Concepts, Types of testing
Topics we will cover in this article:
- Application Testing
- Categories of Applications
- Application Testing Methodologies
- Application Testing Tools
- Software Test Plan
- Application Testing Cycles
- Application Testing – Best Practices
Application Testing is an activity that every software tester performs daily in his career. These two words are extremely broad in practical aspect. However, only the core and most important areas will be discussed here. The purpose of this article is to touch all the primary areas so that the readers will get all the basic briefing at a single place.
Categories of Applications
Whether it is small calculator software with only the basic arithmetic Continue reading →
April 18th, 2010 — Basics of Software testing, Manual Testing, Quality assurance, Testing best practices
Note: If you missed the first part of this post please read it: Why Documentation is important in testing?
As I mention in my earlier post, in general, understanding about software testing documentation is “It can be done only by the person who has free time”. We need to change this mindset, and then only we can leverage documentation power on our projects.
It’s not that we don’t know how to do the documentation right. We just don’t think it’s important.
Everyone must have standard templates for all the kinds of documentation starting from Test strategy, test Plan, Test cases, and Test data to Bug report. These are just to follow some standards (CMMI, ISO etc.) but, when it comes to actual implementation how many of these documents are really used by us? We just need to synchronize our quality process with documentation standards and other process in an organization.
Continue reading →
August 22nd, 2008 — Basics of Software testing, Software Testing Books, software testing links
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 follow these 3 easy steps
What is your favorite software testing book? Also share your ‘best software testing book’ experience with our readers.
May 31st, 2008 — Basics of Software testing, Questions & answers, Testing Concepts, Testing Interview questions
Despite of hundreds of web articles on Smoke and sanity testing, many people still have confusion between these terms and keep on asking to me. Here is a simple and understandable difference that can clear your confusion between smoke testing and sanity testing.
Here are the differences you can see:
- Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
- A smoke test is scripted, either using a written set of tests or an automated test
- A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
- Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
- Smoke testing is normal health check up to a build of an application before taking it to testing in depth.
- A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
- A sanity test is usually unscripted.
- A Sanity test is used to determine a small section of the application is still working after a minor change.
- Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
- Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.
Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.
Thanks to VijayD for answering this question in simple way for our readers.
If you have more points on smoke and sanity testing to elaborate on, please comment below.