Functional testing examines the right handling of the external functions of software product, with the help of monitoring the program external behavior at the time of implementation.

The Meaning of Functional Testing In Software Project

Software is treated as a black-box, with the external behavior monitored through its input and output. That is why it is generally referred to as black-box testing. So these 2 terms can be used interchangeably.

The easiest way of black-box testing is to begin running the software and monitor in the hope that it is easy to differentiate expected and unexpected behavior. Such way ofsoftware testing is considered as ad hoc testing as well.

Such unexpected behavior, as a crash, is easy to identify. As soon as we define that it is caused by software through repeated implementation to eliminate the probabilities of hardware troubles, we can pass the information to responsible parties to have the defect corrected. Actually, this is the general way through which defects found by clients are reported and corrected.

It is also another general way of black-box testing. It is the use of specification checklists, which list the external functions that are supposed to be present, as well as some information about the expected behavior or input-output pairing.

The term input means any action or resource in the process of running a program.

The term output means any action or result produced by the running program.

Concrete samples of input to a calculator might comprise the specific numbers entered and the action requested, such as division operation of 2 numbers. The output could be the actual division result, or some error message, such as when trying to divide by zero. When defects are observed, specific follow-up actions are conducted to correct them.


http://qatestlab.com/

Share
Related Documents
  1. The Meaning of Functional Testing In Software Project. Part II (4477)
  2. Definitions and Meaning: Error, Fault, Failure and Defect (4769)
  3. Software Test Efficacy. Meaning and Calculation (3856)
  4. Safety Assurance And Failure Scope (3730)
  5. Software Fault Tolerance Methods (4552)
  6. Risk Identification Methods In Software Testing (4100)
  7. Software Bug Handling Process And Tools (4635)
  8. What Is Documentation Testing? (2951)
  9. Software Projects Analysis And Design (3571)
  10. Test Documents In The Software Development Lifecycle (3609)
  11. What Is Defect Removal Efficiency In Software Testing? (4351)
  12. Quality Assurance In Software Development Stage (3958)
  13. Main Software Testing Techniques (3784)
  14. Software Bug Handling In Various Quality Assurance Activities (3882)
  15. How Can We Reach Quantifiable Quality Improvement? (4175)
  16. Operating with Pre-/Post-Release Software Bugs (4081)
  17. Requirements-Based Testing (6566)
  18. Waterfall Process In the Quality Assurance Activities (4367)
  19. Direct And Indirect Quality Measures (4253)
  20. Quality Estimation And Improvement (4369)