Skip to main content

Software Testing Module 2

 Functional & Non-Functional Software Testing

What is Functional Testing?

=> Functional testing is a type of software testing that verifies whether each feature And functions of a software application work as per the specified requirements. It is a Black-Box testing method meaning the tester is not connected of the internal coding but only how applications work externally.

Example: website payments Gateway working as required, form submission, navigation & UI.

There are six types of Functional testing

1. Unit Testing:

Testing one small part of the software to check if it works correctly.

Example: Checking if a calculator adds two numbers correctly.

2. Integration Testing:

Testing how different parts of the software work together.

Example: Checking if the login page correctly connects with the database.

3. System Testing:

Testing the complete software system as a whole.

Example: Testing the entire app to check login, dashboard, and logout work properly.

4. User Acceptance Testing (UAT):

Testing done by end users to confirm the software meets their needs.

Example: Customers checking a shopping app before it is officially launched.

5. Regression Testing:

Testing the software again after changes to ensure existing features still work.

Example: Checking login works properly after adding a new feature.

6. Smoke Testing:

Quick testing to check if the main features of the software work.

Example: Checking if an app opens and the login screen loads.


What is Non-Functional testing?

=> Non-functional testing Test Tests the performance speed security usability and reliability of an application.

Example: checking how fast a website loads 1000 users use it at the same time.

There are six types of Non-Functional testing

1. Performance testing

2. Security testing

3. Usability testing

4. Scalability testing

5. Compatibility testing

6. Reliability testing

Comments

Popular posts from this blog

Software Testing Module 1

 Software Testing is a process in which identifying  Completeness, Correctness, Security & Quality of software product takes place. A software Tester must require a very different mindset from a developer. Software Testing means that checking software or a application to make sure that it work properly before people start using it. It helps in application to make it Reliable, Secure with user expectations for Business alignment. The developer only builds the product as per the user needs but the tester need to check or test it from user or customer point of view whether it meets needs of user or not. Software Testing is not just about finding Bugs, its about building trust, delivering excellence, values & a relation, reliable to user experience. What is Software Application? Software Application is a set of programs designed to perform a specific task for a specific user. For example web browsers, MS office, Gmail, Makemytrip and so on the list is never ended. Advantag...

Assignment-1

Assignment-1 1. What is the use of Six Sigma certificate? Ans:-  A Six Sigma certificate is useful for learning how to improve quality and reduce mistakes in any process—whether in software, manufacturing, business, or services. In simple words, Six Sigma teaches you how to do work in a better, faster, and error-free way . Main Uses of a Six Sigma Certificate Helps in Better Career Opportunities Improves Problem-Solving Skills Reduces Errors and Waste Useful in Many Fields Six Sigma Example :  A company uses Six Sigma to reduce defects and improve efficiency in its operations. 2. What is the use of ISO certificate? Ans:- An ISO certificate shows that a company or organization follows international standards for quality, safety, and efficiency in its work. In simple words, it tells customers, This company works in a proper, safe, and trusted way. Main Uses of an ISO Certificate Improves Quality of Products & Services Builds Customer Trust Helps in Getting More Busines...

Software Testing Module 3

V Model 1. Verification (Static Testing) (Left arm of V model) Definition: Verification is the process of checking whether the software is being developed correctly according to the requirements without executing the code. Like: "Are we doing the job right"? What Verification Checks Requirements are clear and complete Design matches requirements Code follows design standards Documents are correct and consistent How Verification is Done Requirement reviews Design reviews Code reviews Walkthroughs & inspections Key Characteristics Static process (no code execution) Done early in SDLC Prevents defects rather than finding them later Saves time and cost Example:   If the SRS says “Password must be at least 8 characters,” verification checks whether this rule is correctly written and included in the design and code documents. Diagram: SRS (Requirements)         ↓      Design         ↓       Code    ...