vividus | VIVIDUS is all in one test automation tool | Unit Testing library

You could use shiftDate expression; It takes three parameters:

1. the date
2. the date formate (see the format)
3. desires shift durations (see the duration)

Please see an example:

Vividus is using Gradle as a build system and the problem described here Your test project exceeds the default Jar size of 4 GB;

To fix the issue please set the following property to a Jar task in your build.gradle file;

Vividus has different timeouts you could configure to synchronize your application and the tests;

Common:

1. bdd.story-execution-timeout - defines the maximum time for a story execution in seconds (default value 10800)
   

plugin-db:

1. db.query-timeout - defines the maximum time for a DB query execution, uses ISO-8061 (default 30 minutes);
   

plugin-web-app

1. selenium.grid.capabilities.bstack:options.idleTimeout - defines how long Browserstack will wait for a command in seconds. (default 360)
   
2. selenium.timeout.async-script-timeout
   selenium.timeout.async-script-timeout-unit - defines timeout for asynch script execution and a time unit, for example SECONDS or MINUTES (default 1 minute)
   
3. selenium.timeout.page-load-timeout
   selenium.timeout.page-load-timeout-unit - defines how long Vividus will wait for a web page to load (default 1 minute)
4. web.alert.wait-for-alert-timeout - defines how long Vividus will wait for alert. Uses ISO-8061 format (default PT0S);
5. web.search.wait-for-element-timeout - defines how long Vividus will try to search an element Uses ISO-8061 format (default PT0S);
   
6. web.wait.page-starts-to-load-timeout - defines how long Vividus will wait before checking page load status, Uses ISO-8061 format (default PT10S);
7. web.wait.polling-period - defines a time period to recheck wait condition Uses ISO-8061 format (default PT2S);
   

8. web.wait.timeout - defines a timeout which will be used for the wait steps, like

   When I wait until element located $locator appears

   Uses ISO-8061 format (default PT1M);
   

plugin-rest-api

1. http.connect-timeout - defines the timeout to establish the connection with the remote host (default value 30000 in millis)
   
2. http.connection-request-timeout - defines the timeout until a request will be executed (default value 30000 in millis)
   
3. http.socket-timeout - defines the socket timeout in milliseconds, which is the timeout for waiting for data or, put differently, maximum period inactivity between two consecutive data packets). A timeout value of zero is interpreted as an infinite timeout.(default value 300000 in millis)

Vividus allows to run Story-level Examples in parallel.

• Define Examples table in story Lifecycle, e.g.:

Please ensure that you have a vividus-plugin-datetime dependency in the build.gradle file as the following example shows:

Vividus DB plugin vividus-plugin-db is based on JDBC thus Vividus supports any DBMS providing JDBC driver. Most of these databases are relational, however some NoSQL databases also provide JDBC drivers.

To configure DB access it's required:

• to add the corresponding plugin to the dependencies:

First of all, Vividus follows Semantic Versioning and adopts all its rules and requirements.

A release version is the final build for the given version published to JCenter. A snapshot is the version being developed and regularly published to OSS JFrog Artifactory. More details regarding release vs snapshot versions can be found in the corresponding question.

Release version of Vividus

Pros:

• stable
• never changed
• determined set of available features

Cons:

• new features and bug fixes are not available immediately
• requires some effort to update to the latest release versions

Snapshot version of Vividus

Pros:

• new features and bug fixes are published regularly and available for use instantly

Cons:

• unstable: may contain new bugs
• no possibility to stick to some known good build

Vividus provides a range of various plugins. Gradle is used as a build tool, so you just need to add a new Gradle dependency.

Let's take Vividus starter project as example. All dependencies are declared in build.gradle:

The recommended approach:

• Find the link on the Web UI
• Extract the link URL
• Use vividus-plugin-rest-api steps to download the file (you may also need to inject cookies from the browser to Web UI using vividus-plugin-web-app-to-rest-api steps)
• Validate HTTP response code and content

Example of the implementation: