Wednesday, April 18, 2007

NFR Testing

NFR Testing:--

Non-Function Requirement Testing is a type of testing in which test user test only "Requirements".


It is not linked to core functions, it just test the requirements.

Non-Functional Requirement (NFR) testing, also known as Non-Functional Testing, focuses on evaluating the attributes of a software system that are not directly related to its functional behavior. NFRs define the qualities and characteristics of a system, such as performance, usability, security, reliability, scalability, maintainability, and compatibility.

NFR testing aims to ensure that the software system meets these non-functional requirements and performs optimally in real-world scenarios. Here are some common types of NFR testing:

Performance Testing: This type of testing evaluates how well the system performs under various workloads and measures its response time, throughput, scalability, and resource usage.

Usability Testing: Usability testing focuses on assessing the user-friendliness of the system, including ease of navigation, intuitiveness, and user satisfaction.

Security Testing: Security testing involves identifying vulnerabilities and weaknesses in the system's security measures, such as authentication, authorization, data protection, and protection against potential threats.

Reliability Testing: Reliability testing aims to ensure that the system operates consistently and reliably over a specified period and under varying conditions, including stress testing, load testing, and stability testing.

Scalability Testing: This type of testing assesses the system's ability to handle increased workload, user concurrency, or data volume and maintain its performance.

Maintainability Testing: Maintainability testing examines how easy it is to maintain and support the system, including aspects such as code readability, modularity, and the ability to make changes or fixes efficiently.

Compatibility Testing: Compatibility testing verifies that the software system functions correctly across different platforms, browsers, operating systems, and hardware configurations.

NFR testing helps ensure that the software system not only meets functional requirements but also delivers the desired performance, usability, security, and other non-functional aspects. By thoroughly testing these non-functional requirements, organizations can enhance the overall quality and user experience of their software systems.

Thursday, March 01, 2007

Test Plan Contents

Test Plan contents:--

1) Test Objectives.
2) Test Strategy.
3) Test Environments.
4) Test Specifications.
5) Test Schedule.
6) Test Plan Review.

Tuesday, February 27, 2007

Static Testing and its Examples

Static Testing:-- Static Testing is a type of testing in which tester checks the code only, he did not run the code to see its output.

Examples:-- Syntax Checking ; Structure Investigation ; Inspection.

Friday, January 19, 2007

Testing Mines

Testing Mines

Shark Tooth:-

In nut shell it consists of many design reviews and many check to get the final product.

Tuesday, October 17, 2006

WHAT IS A GOLDEN BUG ?

Golden bug is nothing but the chasm between our perception and reality.

Monday, September 18, 2006

What is the difference between QA Tester & QA Analyst?

What is the difference between QA Tester & QA Analyst?
A QA Tester deals with the functionality testing basing on the FRS, whereas QA Analyst is the person who is responsible to prepare the Functionality Requirement specification.

The USB-C Moment for AI: A Student’s Guide to the Model Context Protocol (MCP)

  The USB-C Moment for AI: A Student’s Guide to the Model Context Protocol (MCP) In the rapidly evolving world of Artificial Intelligence, ...