domain and service layer tests should not use code from web.rest layer

[kaidohallik]

Overview of the issue

#10686 moved Entity and DTO tests away from web.rest layer but related TestUtil remained in web.rest layer.

generator-jhipster/generators/java/generators/domain/templates/src/test/java/_package_/_entityPackage_/domain/_persistClass_Test.java.ejs

Line 34 in 0fe9a40

import <%= packageName %>.web.rest.TestUtil;

generator-jhipster/generators/spring-boot/templates/src/test/java/_package_/_entityPackage_/service/dto/_dtoClass_Test.java.ejs

Line 23 in 0fe9a40

import <%= packageName %>.web.rest.TestUtil;

Additional note: #10686 moved entities domain/service layer tests from web.rest layer to domain/service layer but missed moving User entity tests from web.rest layer to doamin layer:

generator-jhipster/generators/spring-boot/templates/src/test/java/_package_/_entityPackage_/web/rest/UserResourceIT.java.ejs

Line 894 in 0fe9a40

void testUserEquals() throws Exception {

Motivation for or Use Case

domain and service layers should not depend on web.rest layer

Reproduce the error

Related issues

Suggest a Fix

1. wrong layer usage possible solutions:

• possible solution 1: move TestUtil from web.rest to tests root
• possible solution 2: create DomainTestUtil, ServiceTestUtil and rename TestUtil to RestTestUtil

2. User entity tests in wrong package solution: extract User entity tests from web.rest layer to domain layer as this was done for entities in refactor entity's integration test class #10686

JHipster Version(s)

Current main branch, version 8.7.1

JHipster configuration

To provide all information we need, you should run jhipster info in the project root folder (or workspaces root for microservices), and
copy/paste the result here.
jhipster info removes sentitive information like rememberKey, jwtSecretKey. Double check if there is any other sensitive info.

As alternative you can add a JDL wrapped in below structure

JDL definitions

     JDL content here
  

The information is mandatory for bug reports. This will allow us to use automated tests and genarate the broken sample using jhipster from-issue command.

Browsers and Operating System

• Checking this box is mandatory (this is just to show you read everything)

[mraible]

Can you please create a PR? Maybe this is something we should test with ArchUnit.