here https://www.testcontainers.org/supported_docker_environment/

Hey Guys,
I see an IllegalStateException when running one particular test.

What steps will reproduce the problem?
The following code fails each time it is run

Testcase:

package backend.model.posting

import backend.controller.exceptions.ConflictException
import backend.model.location.Location
import backend.model.user.UserAccount
import org.junit.Before
import org.

Summary

ShouldContainOnly is used in a few places where we know what kind of elements we are dealing with, in this case instead of using the term element we could use a more descriptive name.

Example

Spliterator<?> actual = createSpliterator(SORTED | ORDERED);
spliterators.assertHasOnlyCharacteristics(INFO, actual, DISTINCT, SORTED);

fails with this error

I would like to drop Spring Boot support for 1.5.x. It is EOL https://spring.io/blog/2018/07/30/spring-boot-1-x-eol-aug-1st-2019
I would also add some notes in the docs, that we adhere to the spring boot lifecycle in order to be transparent about dropping support for versions.

Currently, the JDBC string containing the host name and port is hardcoded. For example, consider the connection string for MySQL:

https://github.com/sqlancer/sqlancer/blob/e62224edcb43fe421dc87601f75090739e34e595/src/sqlancer/mysql/MySQLProvider.java#L248

It would be desirable to make this configurable. We could provide an option to set the JDBC string for each DBMS. For example, for MySQL,

As a SDET
I want a documentation or Wiki page where the expected vs actual field matching is explained
So that I can use these in my test automation to test the server response payloads and headers
e.g. id=123 , id="123", isValid=true, isValid="true" etc

AC1:

Cover the following currently supported mechanisms with examples

• $EQ
• (int)
• (float) or (decimal)
• (boolean)