Software Project Planning

This testing is similar to the ad-hoc testing and is done in order to learn/explore the application.

Exploratory software testing is a powerful and fun approach to testing. In some situations, it can be orders of magnitude more productive than scripted testing. At least unconsciously, testers perform exploratory testing at one time or another. Yet it doesn't get much respect in our field. It can be considered as "Scientific Thinking" at real time

Testing of software can broadly classified into Black Box Testing and White Box Testing.

1. Black Box Testing
Functional Testing

Stress Testing

Load Testing

Ad-hoc Testing

Exploratory Testing

Usability Testing

Smoke Testing

Recovery Testing

Beginners Guide To Software Testing introduces a practical approach to testing software. It bridges the gap between theoretical knowledge and real world implementation. This article helps you gain an insight to Software Testing - understand technical aspects and the processes followed in a real working environment

The term 'Black Box' refers to the software, which is treated as a black box. By treating it as a black box, we mean that the system or source code is not checked at all. It is done from customer's viewpoint. The test engineer engaged in black box testing only knows the set of inputs and expected outputs and is unaware of how those inputs are transformed into outputs by the software.

Types of Black Box Testing Techniques: Following techniques are used for performing black box testing

1) Boundary Value Analysis (BVA)

2) Equivalence Class Testing

3) Decision Table based testing

4) Cause-Effect Graphing Technique

This article will provide a brief introduction and overview of software testing, discuss both manual and automated testing, and introduce the concept of blended testing. It is intended as a brief primer on the software testing process.
Software testing is both a discipline and a process. Though software testing is part of the software development process, it should not be considered part of software development. It is a separate discipline from software development. Software development is the process of coding functionality to meet defined end-user needs. Software testing is an iterative process of both validating functionality, and, even more important, attempting to break the software. The iterative process of software testing consists of:

Designing tests
Executing tests
Identifying problems
Getting problems fixed

Test Documentation. (IEEE) Documentation describing plans for, or results
of, the testing of a system or component, Types include test case specification,
test incident report, test log, test plan, test procedure, test report.

This tutorial covers the basics of software testing with accents on white and black box techniques that are mandatory knowledge for certifications. The combination of this tutorial and our full version of the testing dictionary give a good coverage some of the topics for certification.

In this tutorial you will learn about Effective Software Testing? How do we measure 'Effectiveness' of Software Testing? Steps to Effective Software Testing, Coverage and Test Planning and Process.

This article gives an overview of Software Quality Management and various processes that are a part of Software Quality Management. Software Quality is a highly overused term and it may mean different things to different people. You will learn What is Software Quality Management?, What does it take to Manage Software Quality?, Quality Planning, Quality Assurance, Quality Control, Importance of Documentation and What is Defect Tracking?

This article aims to study the process of Software Cost Estimation and its impact on the Software Development Process. We also highlight the various challenges involved in Software Cost Estimation and common solutions to navigate through these challenges.