runtest | Numerically tolerant end-to-end test library

public WebDriver driver;

This declares a field, named driver. Not sure why you made it public.

WebDriver driver = new ChromeDriver();

This declares a local variable, also named driver, which is completely unrelated to the field you declared. As all local variables go, it ceases to exist when the method you declared it in ends. Because it has the same name, referencing variable driver in this method refers to the local variable and not the field.

All you really wanted was to make that second line:

Be sure to execute make after modifying the source code.

You will not see serverLog() messages when you execute the test runner; they are from redis-server.

For test runs, redis-server logs are written to tests/tmp//stdout.

Development cycle:

1. Edit source code
2. Write tests
3. Compile source code
   • make
4. Run tests
   • ./runtest (add your arguments)
5. Inspect redis-server logs
   • less tests/tmp/*/stdout
6. Delete test artifacts
   • rm -rf tests/tmp/*

The issue is known to the mockito project and reported there: https://github.com/mockito/mockito/issues/2316

You'd need to accept the defined parameters as argument in you test case and then use them.

https://github.com/cucumber/cucumber-jvm/tree/main/junit-platform-engine#use-the-cucumber-annotation

Cucumber will scan the package of a class annotated with @Cucumber for feature files. To use this feature, add the @Cucumber annotation to the test runner. Doing so will make Cucumber run the feature files in the package containing the test runner.

So because your annotated class is in the com.example.demo package put the features in src/test/resources/com/example/demo.

First of all, running tests should be done via the go test command.

Certain types and functions exported in the testing package are for the testing framework, not for you. Quoting from testing.RunTests():

RunTests is an internal function but exported because it is cross-package; it is part of the implementation of the "go test" command.

It "had" to be exported because it predates "internal" packages.

There. You've been warned.

If you still want to do it, call testing.Main() instead of testing.RunTests().

For example:

Infact, the problem here is that the automatic generation of the itemId does not work when it is specified inside the composite EmbeddedId (which is "assignment"-based).
(Trying to just save an order with only one item would get you a clearer error message revealing the root problem.)

The automatic generation of ID values inside of embedded IDs does not seem to work as one would expect, as various (old) discussions of this topic show, e.g.:

Hibernate composite key id generator

How can I use generated value within composite keys?

Also see Chapter 6.2. Composite identifiers of the official documentation.

A common workaround involves moving the generated field directly into the entity and using an @IdClass: https://vladmihalcea.com/how-to-map-a-composite-identifier-using-an-automatically-generatedvalue-with-jpa-and-hibernate/

E.g.:

I thought my compiler is smart enough to align the code correctly.

As you said, the compiler is always aligning things to a multiple of 16 bytes. This probably does account for the direct effects of alignment. But there are limits to the "smartness" of the compiler.

Besides alignment, code placement has indirect performance effects as well, because of cache associativity. If there is too much contention for the few cache lines that can map to this address, performance will suffer. Moving to an address with less contention makes the problem go away.

The compiler may be smart enough to handle cache contention effects as well, but only IF you turn on profile-guided optimization. The interactions are far too complex to predict in a reasonable amount of work; it is much easier to watch for cache conflicts by actually running the program and that's what PGO does.

Your problem must be related to Fail to convert to internal representation. You must be making some mistake in the mapping between your entity and DB table. Refer the following link java.sql.SQLException: Fail to convert to internal representation