Explain STLC with an example

 Software Testing Life Cycle (STLC) is a sequence of specific activities conducted during the testing process to ensure software quality goals are met. STLC involves both verification and validation activities. Contrary to popular belief, Software Testing is not just a single/isolate activity, i.e. testing. It consists of a series of activities carried out methodologically to help certify your software product. STLC stands for Software Testing Life Cycle.

STLC Phases

There are following six major phases in every Software Testing Life Cycle Model (STLC Model):

STLC Phases
STLC Model Phases
  1. Requirement Analysis
  2. Test Planning
  3. Test case development
  4. Test Environment setup
  5. Test Execution
  6. Test Cycle closure

Comments

Post a Comment

Popular posts from this blog

What is a client and a server?

Image
A client is a piece of software or hardware for a computer that uses a server-provided service. Usually (though not usually), the server is housed on a different physical computer. A physical computer that is devoted to providing services to meet the needs of other computers is called a server. It could be a file server, database server, print server, web server, or home media server, depending on the service that is operating. One type of web client is your web browser. A protocol called HTTP is used by a client and server to interact.
Read more

What is a use case?

A use case is a description of how a user interacts with a system or product. Companies build use cases to establish success scenarios, failure scenarios, and any important variants or exceptions. Many organizations leverage use case modeling tools — such as Miro, LucidChart, and SmartDraw, for some examples — to write or visually represent a use case. Use cases are frequently employed in software development environments to simplify complicated concepts, but they can be just as important in project management for gathering requirements and defining a project’s scope.
Read more

Difference between system, Integration and E2E test

  System Testing This stage of testing verifies that the software product is integrated and whole. A system test's objective is to assess if the requirements and specifications are being followed. Typically, software is just a small part of a bigger computer system. In the end, the program interfaces with hardware and/or software systems. Actually, system testing is a set of tests designed specifically to put the entire computer-based system through its paces. System testing looks for flaws in the system overall as well as in the "inter-assemblages." The behavior that is generated or seen during testing of a system or component is the actual outcome. Integration Testing Integration testing is a kind of testing in which systems or software modules are tested collectively and logically integrated. Several software modules written by various programmers make up a typical software project. This level of testing aims to reveal flaws in how various software modules interact wit
Read more