anchor.diff:      NAME: "groovy:(value != null && value.contains('@dbunit'))"
   ```
   
  -To enable the scripting you mainly need the `js: or groovy:` prefix *followed by an expression which evaluates to boolean* inside a `parentheses`.
  +To enable the scripting you mainly need the `js: or groovy:` prefix *followed by an expression which evaluates to boolean* inside a `parentheses`. The `value` in the expression refers to the actual value that should be in database after the test runs.
   
   ```
       @Test
  
positive.code: <dependency>
        <groupId>com.github.database-rider</groupId>
        <artifactId>rider-core</artifactId>
        <version>1.30.0</version>
        <scope>test</scope>
  </dependency>
  ----
  
negative.code: 
  ==== Using `script assertions` in expected datatset
  
  Since `v1.31.0` it's possible to use javascript or groovy assertions (based on <<Scriptable DataSets>>) in `@ExpectedDataSet`, for example consider the following dataset:
  
  ```
  USER:
  