New JHipster project: All integration tests fail

By -

Today, I tried starting a new project using JHipster. My environment includes:

Windows 10 22H2 build 19045.2251 (64 bit)
OpenJDK Runtime Environment Temurin-16.0.2+7
node 16.17.0
npm 8.19.1
Gradle 7.5.1
MariaDB 10.6.8
Chrome 107.0.5304.107

Project configuration file (myapp.jh) is:

application {
  config {
    baseName myapp,
    packageName com.mycompany.app,
    applicationType monolith,
    authenticationType jwt,
    cacheProvider ehcache,
    enableHibernateCache true,
    databaseType sql,
    devDatabaseType mariadb,
    prodDatabaseType mariadb,
    buildTool gradle,
    clientPackageManager npm,
    clientFramework angular,
    clientTheme minty,
    clientThemeVariant primary,
    testFrameworks [protractor, cypress],
    nativeLanguage en,
    languages [en, es],
    jhiPrefix myapp,
    jwtSecretKey "YjAwZDU2ODI3NzNjZjk0NjVhY2UzNGViZmY0YjY1ZGY2MDI5MTc5Y2FlZWYxNzE5Yjg5ZjMxOGZhZTgwZjA5NTFkN2VmNDM3ZGMyZDNjZTViNDAwYTg4NmNlMmM2ZDkxZTMwMDk5YmUxNWNkZmE0YTNiNDlhMGNhZmM4OTk1NmQ="
  }
}

I carried out the following steps in a shell command line:

  • Installed the latest version of JHipster: npm install -g generator-jhipster --> v7.9.3
  • Imported the JDL: jhipster jdl myapp.jh
  • Built the application: gradle build

Result: Everything appears to build nicely up until the integration tests which ALL fail!

All integration tests for the latest version of JHipster fail in virtually the same way:

HibernateTimeZoneIT > storeLocalDateTimeWithZoneIdConfigShouldBeStoredOnGMTTimeZone() FAILED
    java.lang.IllegalStateException at DefaultCacheAwareContextLoaderDelegate.java:132
        Caused by: org.springframework.beans.factory.BeanCreationException at AbstractAutowireCapableBeanFactory.java:1804
            Caused by: java.lang.IllegalStateException at DockerClientProviderStrategy.java:257

Naturally, the first line of each error varies according to each failing test, but the following lines (java.lang.IllegalStateException ... onward) are the same for ALL failed tests. I have never seen errors like this before. It appears to have something to do with Docker.

I repeated the steps for JHipster 7.9.2, and 7.9.0 -- with the same results -- all integration tests fail. (I even tried the maintenance build for 7.9.3, and get the same failures.) I also get the same errors if I run the integration tests directly with: gradle integrationTest

Finally, I downgraded to JHipster 7.8.1 (released in April), and everything works (no failures).

Are the last three JHipster releases (7.9.0, 7.9.2 and 7.9.3) broken? Has there been a new requirement introduced after v7.8.1? Am I doing something wrong?

Please help!

(I'm happy to provide ANY additional information.)

NOTE: If I forego the integration tests, and just run the application (by typing ./gradlew in one shell, and npm start in another shell, the application does run/work...)



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch")....
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk....
Read more