Bot releases are visible (Hide)
@Micky002 @vaa25
Published by rmpestano 3 months ago
@tomlux @netmikey @coiouhkc @diqksrk
Published by rmpestano 7 months ago
@beskow @xak2000 @tomlux
Published by rmpestano 8 months ago
Make sure to declare rider-core
and rider-junit5
with jakarta classifier:
<dependency>
<groupId>com.github.database-rider</groupId>
<artifactId>rider-junit5</artifactId>
<version>1.41.1</version>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>com.github.database-rider</groupId>
<artifactId>rider-core</artifactId>
</exclusion>
</exclusions>
<classifier>jakarta</classifier>
</dependency>
<dependency>
<groupId>com.github.database-rider</groupId>
<artifactId>rider-core</artifactId>
<version>1.41.1</version>
<scope>test</scope>
<classifier>jakarta</classifier>
</dependency>
@jowko
Published by rmpestano about 1 year ago
Published by rmpestano about 1 year ago
Now both rider-core
and rider-cdi
have the jakarta
maven classifier
@abigailCortis @HongHanh9527
Published by rmpestano over 1 year ago
@mdiachuk
Published by rmpestano over 1 year ago
To use rider-cdi with quarkus 3 or any Jakarta application, enable the jakarta
classifier in rider-cdi:
<dependency>
<groupId>com.github.database-rider</groupId>
<artifactId>rider-cdi</artifactId>
<version>1.38.1</version>
<scope>test</scope>
<classifier>jakarta</classifier>
<exclusions>
<exclusion>
<artifactId>stax-api</artifactId>
<groupId>stax</groupId>
</exclusion>
</exclusions>
</dependency>
@DeMol-EE @mkwapisz @matjazs
Published by rmpestano over 1 year ago
@vladimirfx
Published by rmpestano over 1 year ago
Published by rmpestano almost 2 years ago
@opengl-8080 @bergerst @niels1voo
Published by rmpestano almost 2 years ago
@coiouhkc
Published by rmpestano about 2 years ago
@netmikey
Published by rmpestano about 2 years ago
In this release, we updated DBUnit to 2.7.3
and replaced org.codehaus.jackson
by jackson-databind
.
@trks1970
Published by rmpestano over 2 years ago
clearDatabase
does not take table ordering into account (#417)@vincentstradiot
Published by rmpestano over 2 years ago
@vkrauze @JapuDCret @bergerst @jpbassinello
Published by rmpestano almost 3 years ago
@entireboy
Published by rmpestano almost 3 years ago
@duschata
Published by rmpestano about 3 years ago
@ExpectedDataSet
(#358)This release enables the use of javascript or groovy assertions in @ExpectedDataSet
, for example, consider the following dataset:
USER:
- ID: "js:(value > 0)"
NAME: "js:(value != null && value.contains('@realpestano'))"
- ID: "groovy:(value > 0)"
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
. The value
in the expression refers to the actual value that should be in database after the test runs.
@Test
@DataSet(value = "yml/empty.yml", transactional = true)
@ExpectedDataSet(value = "yml/expectedUserWithScripting.yml")
public void shouldEvaluateScriptsInExpectedDataSet() {
User u = new User(1);
u.setName("@realpestano");
User u2 = new User(2);
u2.setName("@dbunit");
em().persist(u);
em().persist(u2);
}
@coiouhkc