BUILD FAILURE on running mvn clean install on openmrs-contrib-qaframework

i ran into a build failure block on step 3 of the QA Framework: Technical documentation (Cucumber-Selenium & Cucumber-Cypress Set up). There are two files created at C:\Users\pc\openmrs-contrib-qaframework\target\surefire-reports and here are the contents of org.openmrs.contrib.qaframework.RunTest!

@kdaud kindly take a look!

@insookwa do you mind sharing your experience on this epic and perhaps give guidance to @mherman22 to see him sorted ?


@mherman22 did you get a chance to take a look at this talk post here ?


specificaly @kdaud advise here may be the first step

1 Like

As well the next comment here should be looked into!

1 Like

To add on @kdaud suggestions, You can try changing headless to false and see if that helps, Check with your chrome version to be 89.above as well.

i pulled the recent changes as advised and followed every thing to the latter but still got the same issue

thanks, however im still blocked. This is what i did, installed node, and refreshed the cmd. then did an npm install to get all the dependencies.

However when i try to run npm run refappCypress i get `

openmrs-contrib-qaframework@0.1.0 refappCypress C:\Users\pc\openmrs-contrib-qaframework cypress-tags run -eTAGS=’@cypress and not @microfrontend’

Using cypress.json configuration:
Spec files:  {src/test/resources/features/*.feature,src/test/resources/features/**/*.feature}
No matching tags found

`guide me where im messing up.

Share the output for each of the commands below

node -v

npm -v

C:\Users\pc\openmrs-contrib-qaframework>node -v

C:\Users\pc\openmrs-contrib-qaframework>npm -v


Upgrade the npm version to 7.19.0

done! error still persists.

Share the build result summary after triggering one of the existing test workflows for-example:

npm run vitalsAndTriagingTest

Here you go β€”> Build summary

Share the output of the command below

mvn –version

Apache Maven 3.8.1 (05c21c65bdfed0f71a2f2ada8b84da59348c4c5d)
Maven home: C:\opt\apache-maven-3.8.1-bin\bin\..
Java version: 1.8.0_301, vendor: Oracle Corporation, runtime: C:\Program Files\Java\jdk1.8.0_301\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
1 Like

According to the log, the test is unable to collect the respective artifacts from distro and uitestframework module required for the build. You may need to ensure you build uitestframework first and then distro-referenceapplication ensuring their respective builds are successful then run the test again

1 Like

i deleted the artifacts of distro and uitestframework and built openmrs-contrib-uitestframework followed by distro-referenceapplication and they built successfully, then ran the test ( npm run vitalsAndTriagingTest) test against the openmrs-contrib-qaframework.

However, i get a new blocker as shown below :

> openmrs-contrib-qaframework@0.1.0 vitalsAndTriagingTest
> mvn test -Dcucumber.filter.tags='@selenium and @vitals'

[INFO] Scanning for projects...
[WARNING] Some problems were encountered while building the effective model for org.openmrs.contrib:qaframework:jar:1.0-SNAPSHOT
[WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 143, column 21
[WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[INFO] ------------------< org.openmrs.contrib:qaframework >-------------------
[INFO] Building OpenMRS QA Framework 1.0-SNAPSHOT
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  0.340 s
[INFO] Finished at: 2021-08-09T02:10:34-07:00
[INFO] ------------------------------------------------------------------------
[ERROR] Unknown lifecycle phase "and". You must specify a valid lifecycle phase or a goal in the format <plugin-prefix>:<goal> or <plugin-group-id>:<plugin-artifact-id>[:<plugin-version>]:<goal>. Available lifecycle phases are: validate, initialize, generate-sources, process-sources, generate-resources, process-resources, compile, process-classes, generate-test-sources, process-test-sources, generate-test-resources, process-test-resources, test-compile, process-test-classes, test, prepare-package, package, pre-integration-test, integration-test, post-integration-test, verify, install, deploy, pre-clean, clean, post-clean, pre-site, site, post-site, site-deploy. -> [Help 1]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1]

Share the full log report via

Cmd error on running Npm run vitalsAndTriagingTest