EntityGenerator | PHP Based Entity Generator - Used to generate entities | SQL Database library

Spring Test uses a Context Caching mechanism to reuse already started contexts if the context configuration matches. So by default, you should be fine with having one abstract class or just by annotating your tests with @SpringBootTest. The package where the test or production code is in, shouldn't matter.

There are however scenarios where Spring Test will create a new context if you change something for the context configuration e.g. use @MockBean or set the active profile.

Take a look at the official documentation and you can find the list of configuration parameters Spring Test uses to identify a context. If one of these parameters changes throughout your tests, you'll get a new context created.

Also ensure that your tests are executed within the same context and you are not using any forkMode of the Maven Surefire plugin.

You've chosen to generate a reactive app with Spring WebFlux and so you can't use SQL databases because JDBC is blocking and R2DBC is not yet supported by JHipster.

So you have 2 choices: generate a non reactive app and use SQL database or generate a reactive app and use a noSQL database (MongoDB, Cassandra, Couchbase).

I noticed that you're passing a numeric value for RowKey attribute.

When exporting an async function, you can configure an output binding to take the return value. This is recommended if you only have one output binding. See doc

To assign an output using return, change the name property to $return in function.json.

You need a Pojo of following specification.

You only need to create a object of your class. it will automatic populated with random number..

. in column name is not supported. You can use a custom delimiter to flatten your objects instead.

For example:

In your case, stuff is JSON. Table Storage entities don't have a JSON type. You'd need to stringify, resulting in a String type.

You could also choose to use separate properties for each element in your JSON doc (and every entity could contain different properties - no schema is enforced; you'd just need to give yourself a hint on stored object type, so that you could retrieve the properties as needed). And yes, that gets trickier as you continue to nest JSON objects, as your example does.

FYI all supported Table entity types are listed here.

It's because directory structure. You're trying to load EntityGenerator\Database\DatabaseConnection. it's match with path in the first example but not for second one. Just look at the path from autoload.php. It's looking for paths in it's path. EntityGenerator is a valid path in www/entity which's path for autoload.php. But not for www/entity/EntityGenerator at second example.