Installed Maven and python integration test

What am i trying to do

I currently have a Java project that Maven uses when building a system. In an attempt to implement some integration test coverage, I created a python test suite that starts my process, passes data to it, and verifies that the results are all as expected.

This worked well for me, however I am trying to set up my test suite environment correctly. For the test suite to work correctly, I need to locate the JAR file of my executable and determine the correct path to it. All these things are now hardcoded for my workspace.

Workspace layout

├── log
├── src
│   ├── integration-test
│   │   ├── python
│   │   └── resources
│   ├── main
│   │   ├── assembly
│   │   ├── env
│   │   ├── java
│   │   └── resources
│   └── test
│       ├── java
│       ├── resources
│       └── scripts
└── target
    ├── <Service JAR File>

      

Questions

  • I am currently using maven to populate some properties files with settings obtained from the POM using the maven-resources plugin. But this seems to work with static settings. Can this be done? something like this with dynamic settings like the JAR name? Would this be the correct way to get the jar file path for my integration test?
  • What's the ideal way to link my integration tests to maven build process? Ideally, after successful builds, I would like to run my integration tests just like the unit tests. `
+3
java python maven integration-testing


source to share


No one has answered this question yet

Check out similar questions:

5504
Does Python have a ternary conditional operator?
5231
What are metaclasses in Python?
4473
Calling an external command in Python
3790
How can I safely create a subdirectory?
3602
Does Python have a substring method "contains"?
3119
What is the difference between Python list methods that are appended and expanded?
2818
Finding the index of an element by specifying the list that contains it in Python
646
Working with "Xerces hell" in Java / Maven?
478
IntelliJ Inspection gives "Cannot resolve symbol" but still compiles the code
135
Disallow unit tests, but allow integration tests in Maven



All Articles
Loading...
X
Show
Funny
Dev
Pics