Functional Vs Non-Functional Testing

 Functional Vs Non-Functional Testing

1. What is Functional Testing?

Functional testing is a type of testing which verifies that each function of the software application operates in conformance with the requirement specification. This testing mainly involves black box testing, and it is not concerned about the source code of the application.

Every functionality of the system is tested by providing appropriate input, verifying the output and comparing the actual results with the expected results. This testing involves checking of User Interface, APIs, Database, security, client/ server applications and functionality of the Application Under Test. The testing can be done either manually or using automation

2. What is Non-Functional Testing?

Non-functional testing is a type of testing to check non-functional aspects (performance, usability, reliability, etc.) of a software application. It is explicitly designed to test the readiness of a system as per nonfunctional parameters which are never addressed by functional testing.

A good example of non-functional test would be to check how many people can simultaneously login into a software.

Non-functional testing is equally important as functional testing and affects client satisfaction.

3. Difference between Functional Testing and Non Functional Testing

Functional Testing	Non-functional Testing
It verifies the operations and actions of an application.	It verifies the behavior of an application.
It is based on requirements of customer.	It is based on expectations of customer.
It helps to enhance the behavior of the application.	It helps to improve the performance of the application.
Functional testing is easy to execute manually.	It is hard to execute non-functional testing manually.
It tests what the product does.	It describes how the product does.
Functional testing is based on the business requirement.	Non-functional testing is based on the performance requirement.

Read More

Test Scenarios for Image Upload Functionality

 

Test Scenarios for Image Upload Functionality

1. Check for the uploaded image path.

2. Check image upload and change functionality.

3. Check image upload functionality with image files of different extensions (For Example, JPEG, PNG, BMP, etc.)

4. Check image upload functionality with images that have space or any other allowed special character in the file name.

5. Check for duplicate name image upload.

6. Check the image upload with an image size greater than the max allowed size. Proper error messages should be displayed.

7. Check image upload functionality with file types other than images (For Example, txt, doc, pdf, exe, etc.). A proper error message should be displayed.

8. Check if images of specified height and width (if defined) are accepted or otherwise rejected.

9. The image upload progress bar should appear for large size images.

10. Check if the cancel button functionality is working in between the upload process.

11. Check if the file selection dialog only shows the supported files listed.

12. Check the multiple images upload functionality.

13. Check image quality after upload. Image quality should not be changed after upload.

14. Check if the user is able to use/view the uploaded images.

Read More

Test Cases for Error Message

Test Cases for Error Message

1. Check the spelling of the error message is correct or not.

2. Verify the grammar for the error messages is correct.

3. Verify error message for empty field will be displayed.

4. Verify the error message uploading an empty file is displayed.

5. Verify an error message will be displayed for files that are not supported by the system.

6. Verify message when confirming email/phone registration is duplicated or locked

7. Verify an error message will be displayed in case characters out of range.

8. Check the error message that will be displayed for the invalid URL.

9. An error message will be displayed when a captcha is not valid.

10. Verify and check error message will be displayed if captcha is not uploaded (may be affected by network)

11. Verify where the error message should be aligned.

12. A 500 error message page will be displayed to the user. (when affected by Server)

13. Verify the time period for the error message to be displayed.

14. Verify the Alert error messages are not overlapping.

Read More

TEST CASES FOR SEARCH FIELD

 

TEST CASES FOR SEARCH FIELD

  A search field is the common field of any website. Hope below some test cases are helpful for you !

1.   Check the name of search field is correct
   
   
2.   Check whether the the search field can be clicked or not.
   
   
3.   Check whether it is able to type or enter in the search field or not.
   
   
4.   Check placeholder is added to the search field.
   
   
5.   Check the cursor appears after clicking the search icon.
   
   
6.   Check that when the user pastes or copy in the search field.
   
   
7.   Check that when the user can type any alphanumeric, special characters in the search field.
   
   
8.   Check the search function return correct results for the valid keywords.
   
   
9.   Enter any one character in the search field and click on the Search button/press Enter key.
   
   
10.   Enter string more than the max length in search field.
    
    
11.   Enter a string in the search field with spaces (before the string, after the string, and in between) and verify the results.
    
    
12.   Without entering character in the search field then click on the Search button.
    
    
13.   Click in the search field and press Enter key.
    
    
14.   Check the time systems return search results.
    
    
15.   Check the search results are in the correct order as requirement.
    
    
16.   Check if suggestions are shown when adding keywords to the search field.
    
    
17.   Try to drag and drop images, videos or another file in the search field and check the result

Read More