Database Testing, Static and Dynamic Testing

Database Testing:

When we submit the data from the application (Frontend), the data will be inserted into the database.Whether the data is properly inserted into the tables of the database is known as Database Testing.

Example: Create one account in Gmail >> Once it is successfully created, the details will be stored in the database.

 

Static Testing:

Test the application without performing any action is known as Static Testing.

Example:

GUI Testing, Validation.

  • Validation means checking the availability of the fields.

 

Dynamic Testing:

Test the application by performing some action is known as Dynamic Testing.

Example:

Regression Testing, Re – Testing, Adhoc Testing etc.

 

Click here for Functional Testing Types

Click here for Smoke Testing & Pre – SRN Testing

Click here for Sanity, GUI and Validation Testing

Click here for Regression Testing and Re – Testing

Click here for End to End Testing and Monkey Testing

Click here for Compatibility Testing and Usability Testing

Click here for Exploratory Testing and Adhoc Testing

Click here for Authentication Testing, Direct URL & Firewall Leakage Testing

3 Thoughts on Database Testing, Static and Dynamic Testing

  1. Static Testing is reviewing business requirements using formal or informal way- reviews/walk through/inspections.
    Dynamic Testing is executing the code and validating the outcome of the program.

  2. Dynamic Testing is a type of testing when an application needs to be tested for varied sets of inputs (like Test Data or Rules or configurations) or changing criteria. So you change certain inputs into an application and see how the application now performs. Most part of what we perform as software test engineers is Dynamic Testing.

    A good example: If you are testing for an application like a stock market or insurance calculators or weather based wesbsites. You could perform this type of testing using manual steps or automation steps too.

    Static Testing is more standard where you are testing parts of an application that are fairly constant and do not change. This includes Documentation reviews (Functional/Technical specification documents), Code level testing (white-box testing), architecture level testing.

Leave a Comment