ContributionsMost RecentMost LikesSolutionsRe: Can't. open ready API with new mac OS big sur It's ok with update, thanks a lot Re: Can't. open ready API with new mac OS big sur Full log : richie Re: Can't. open ready API with new mac OS big sur While trying to run through terminal : A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007fff203ae0a9, pid=33417, tid=775 # # JRE version: OpenJDK Runtime Environment (12.0.1+12) (build 12.0.1+12) # Java VM: OpenJDK 64-Bit Server VM (12.0.1+12, mixed mode, tiered, compressed oops, g1 gc, bsd-amd64) # Problematic frame: # C [libsystem_platform.dylib+0x10a9] _platform_memmove$VARIANT$Haswell+0x29 # # No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again # # An error report file with more information is saved as: # /Applications/ReadyAPI-3.4.0.app/Contents/java/app/bin/hs_err_pid33417.log 15:45:06,117 WARN [SoapUIProGroovyScriptEngineFactory] Missing scripts folder [/Applications/soapUI-Pro-4.5.2.app/Contents/java/app/bin/scripts] 15:45:06,119 INFO [DefaultSoapUICore] Adding listeners from [/Applications/ReadyAPI-3.4.0.app/Contents/Resources/app/bin/listeners/demo-listeners.xml] 15:45:06,147 WARN [SoapUIJasperReportManager] The report directory is not specified. The default report directory will be used. # # If you would like to submit a bug report, please visit: # http://bugreport.java.com/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. # Re: Can't. open ready API with new mac OS big sur i don't know how to update without opening the application. Here are the logs Can't. open ready API with new mac OS big sur Hello, I updated mac os, and I can't open Ready API 3.4, its show the splach screen then it crashes Cordialy SolvedRe: Need dependency for integrating ReadyApi with Java Maven hank your for your answer: here's how I envoke soapui teststeps : SoapUI.setSoapUICore(new StandaloneSoapUICore(true)); SoapUI.getSettings().setBoolean(HttpSettings.RESPONSE_COMPRESSION, false); WsdlProject project; try { project = new WsdlProject("SoapProjects/" + projectName); tSuite = project.getTestSuiteByName(defaultTestSuite); } catch (XmlException | IOException | SoapUIException e) { e.printStackTrace(); } And WsdlTestCase tc = tSuite.getTestCaseByName("name"); Map<String, String> params = new HashMap<String, String>() { { put("username","sss"); put("ApiVersion","1.0.0" ); put("env",env ); } }; And for (int i = 0; i < tc.getTestStepCount(); i++) { System.out.println(tc.getTestStepCount()); WsdlTestStep ts = tc.getTestStepAt(i); String tsName = ts.getName(); if (!ts.isDisabled()) { WsdlTestCaseRunner runner = new WsdlTestCaseRunner(tc, new StringToObjectMap()); TestStepResult result = runner.runTestStep(ts); .... By the way, I filter on disabled, but it execute them anyway Thanks in advance Need dependency for integrating ReadyApi with Java Maven Hello, I've done a lot of dev with SoapUi (open source version) with this dependency <dependency> <groupId>com.smartbear.soapui</groupId> <artifactId>soapui</artifactId> <version>5.0.0</version> <exclusions> <exclusion> <groupId>javafx</groupId> <artifactId>jfxrt</artifactId> </exclusion> <exclusion> <artifactId>servlet-api</artifactId> <groupId>jetty</groupId> </exclusion> <exclusion> <artifactId>commons-codec</artifactId> <groupId>commons-codec</groupId> </exclusion> <exclusion> <groupId>com.jayway.jsonpath</groupId> <artifactId>json-path</artifactId> </exclusion> </exclusions> </dependency> Now that we bought SoapUi Pro, some testSteps can't be executed in our Java code (I guess because these testStep are only compatible with SoapUi OpenSource testRunner) Is there a way to keep the same code source that we have and integrate the Pro feature, like changing only the dependency ? Thanks Can't access step properties in a REST Post method Hello, I'm trying to access properties from a step called "Properties" The standard use for such case is to do so : but it's not working ! Media type is multipart/form-data and post queryString should be unchecked. any help please ? Solved