Skip to main content
Version: 4.x

The Result Object

Vest validations return a results object that holds all the information regarding the current run and methods to interact with the data.

A result object would look somewhat like this:

'valid': false, // Whether the suite as a whole is valid or not
'errorCount': 0, // Overall count of errors in the suite
'warnCount': 0, // Overall count of warnings in the suite
'testCount': 0, // Overall test count for the suite (passing, failing and warning)
'tests': { // An object containing all non-skipped tests
['fieldName']: { // Name of each field
'errorCount': 0, // Error count per field
'errors': [], // Array of error messages fer field (may be undefined)
'warnings': [], // Array of warning messages fer field (may be undefined)
'warnCount': 0, // Warning count per field
'testCount': 0, // Overall test count for the field (passing, failing and warning)
'valid': false, // Field specific validity
'groups': { // An object containing groups declared in the suite
['fieldName']: { // Subset of res.tests[fieldName]
/*... */ // only containing tests that ran within the group

Result Object methods

Along with this data, our result object also contains a few other methods that can be used to interact with the data:


isValid returns whether the validation suite as a whole or a single field is valid or not.

Suite validity

A suite is considered valid if the following conditions are met:

  • There are no errors (hasErrors() === false) in the suite - warnings are not counted as errors.
  • All non optional fields have passing tests.
  • There are no pending async tests.


Field validity

A field is considered valid if the following conditions are met:

  • The field has no errors (hasErrors() === false) or the field is omitted via the functional "optional" API.
  • All non-optional tests for the field are passing.
  • The field has no pending tests.


When isValid equals false it does not necessarily mean that the form is inValid. It only means that might not be valid yet. For example, if not all the fields are filled, the form is not valid yet, even though it may not be strictly invalid.

hasErrors and hasWarnings

If you only need to know if a certain field has validation errors or warnings but don't really care which they are, you can use hasErrors or hasWarnings functions.

// true

// false

In case you want to know whether the whole suite has errors or warnings (to prevent submit, for example), you can use the same functions, just without specifying a field

// true

// true


Similar to isValid, but returns the result for a specified group. Providing a group name that doesn't exist will return false. When adding a fieldName, only the field within that group will be checked.

resultObject.isValidByGroup('groupName', 'fieldName');

Return Value

Returns a boolean value, whether the group/field combo is valid or not.


groupNamestringYesName of the group
fieldNamestringNoName of the field. When specified, only the result for the specified field within the group is returned.

hasErrorsByGroup and hasWarningsByGroup

Similar to hasErrors and hasWarnings, but returns the result for a specified group

To get the result for a given field in the group:

resultObject.hasErrorsByGroup('groupName', 'fieldName');
// true

resultObject.hasWarningsByGroup('groupName', 'fieldName');
// false

And to get the result for a whole group.

// true

// true

Read more about groups

getErrors and getWarnings

These functions return an array of errors for the specified field. If no field is specified, it returns an object with all fields as keys and their error arrays as values.

// ['Username is too short', `Username already exists`]

// ['Password must contain special characters']

If there are no errors for the field, the function defaults to an empty array:

// []

// []

You can also call these functions without a field name, which will return you an array per field:


// {
// username: ['Username is too short', `Username already exists`],
// password: ['Password must contain special characters']
// }

If you did not specify error messages for your tests, your errors array will be empty as well. In such case you should always rely on .hasErrors() instead.

getErrorsByGroup and getWarningsByGroup

Just like get getErrors and getWarnings, but narrows the result to a specified group.

resultObject.getErrorsByGroup('groupName', 'fieldName');
resultObject.getWarningsByGroup('groupName', 'fieldName');

Read more about groups.


Done is a function that can be chained to your validation suite, and allows invoking callbacks whenever one, or all fields, are finished running - regardless of the validation result.

If we specify a field name in our done call, Vest will not wait for the whole suite to finish before running our callback. It will invoke immediately when all tests with that given name finish running.

.done() calls can be infinitely chained after one another, and as the validation suite completes - they will all run immediately.

done takes one or two arguments:

fieldNameStringYesIf passed, the current done call will not wait for the whole suite to complete, but instead wait for a certain field to finish.
callbackFunctionNoA callback to be run when either the whole suite or the specified field finished running.

The result object is being passed down to the done object as an argument.

In the below example, the done callback for UserName may run before the whole suite finishes. Only when the rest of the suite finishes, it will call the other two done callbacks that do not have a field name specified.

import { create, test, enforce } from 'vest';

const suite = create(data => {
'Marked as spam address',
async () => await isKnownSpammer(data.address)

'must not be blacklisted',
async () => await isBlacklistedUser(data.username)

const validationResult = suite(data)
.done('UserName', res => {
if (res.hasErrors('UserName')) {
.done(output => {
.done(output => {

.done calls must not be used conditionally - especially when involving async tests. This might cause unexpected behavior or missed callbacks. Instead, if needed, perform your conditional logic within your callback.

// 🚨 This might not work as expected when working with async validations

if (field === 'username') {
result.done(() => {
/*do something*/
// ✅ Instead, perform your checks within your done callback

result.done(() => {
if (field === 'username') {
/*do something*/