Basic Test Flow: Back-End Verification

Posted by Albert Gareev on May 24, 2008 | Categories: Patterns

Parent page: Basic Test Flows

Back-End Verification Test Flow


Data File


Entry/Exit Points

Entry Point. Single.

Exit Point. Single. Same as Entry.


GUI interaction – None

GUI observation – None 

Evaluation – assessment of Pass/Fail criteria for comparison.

Pass/Fail Criteria

Fail Criteria

  • Failed to find data record
  • Assessment criteria failure


Stop Criteria

  • DB connection failure
  • File I/O failure
  • Service call failure


Pass Criteria

  • No failures
  • End of steps reached


Test Data

Input Data. None.

Query Data. Hard-coded or parameterized query.

Verification Data. The Test Flow uses verification data to compare against actual data. Verification Data could be hard-coded or combination of hard-coded and parameterized data.


(See pictures on top)


Back-end Verification is a special kind of Test Flow. There are no GUI interactions or observations. Because of that it’s fully static, and can be invoked at any point required from another Test Flow, or even executed in parallel.


Since it’s a non-GUI Test Flow, it should be implemented as a fully isolated function which has common access to Data Model and Reporting Service Functionalities.


The Coverage is in direct dependency on the number of data fields verified.

  • Leave a Reply

    * Required
    ** Your Email is never shared

Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported
This work by Albert Gareev is licensed under a Creative Commons Attribution-NonCommercial-NoDerivs 3.0 Unported.