- Last Active
- Members, Staff
Simpler than that would be to update to version 9.10 - which ships Java 8 by default so you wouldn't need to pass any special arguments to control the Java version.1
You should keep an eye on the Parasoft forum and blog - within the next few weeks we are going to publish a forums post and a blog post which explains how you can integrate SOAtest and Cucumber.2
I am not very familiar with JUnit-Tools but after reading the documentation and trying it out here is what I can say:
JUnit-Tools is a very basic JUnit test generation tool. You can generate basic tests that instantiate the class under test and call the method under test. You can also create some basic mocks but I haven't quite figured out how to use them.
UTA has a lot of obvious advantages to JUnit-Tools:
- UTA builds more logic into the test cases in terms of instantiating or mocking dependent objects.
- UTA automatically creates sample assertions that can be modified by the user; JUnit-Tools generates no assertions.
- UTA can create parameterized tests that exercise the code with different test data inputs; JUnit-Tools has no support for parameterization of which I am aware.
- The tests that get created by JUnit-Tools have compile-time dependencies on the JUnit-Tools jar file; the tests created by UTA can be run independently of any Parasoft libraries.
- UTA has a runtime analysis component that allows you to see what happened at runtime, and it will automatically suggest improvements to your tests while allowing you to visualize what happened during the test run.
- UTA can create test cases in bulk; JUnit-Tools cannot.
- UTA has support for Spring applications - JUnit-Tools does not.
- JUnit-Tools appears to be developed by only 3 people and looks like very little maintenance is being done on the project. UTA has multiple teams of people at Parasoft who research and evolve it.
Also, if a database is not required, UTA within Jtest 10.3.2 will assist you to create parameterized JUnit test cases that pull the data inputs from within code or from a CSV file.2
Actually this is a proxy authentication error. The HTTP Authentication section that Omar pointed to is authentication for the service, not for the proxy. You will likely need to go to the Parasoft Proxy preferences to configure the proxy authentication (Parasoft menu > Preferences... > Proxy).