kendemoor
Occasional Contributor
Joined 7 years ago
User Profile
User Widgets
Contributions
Re: How to run only testcases with a specific tag, in a full regression.
Thanks, That is an interesting workaround and I could see how it could work, but for my specific use case it has some issues since I already disable/enable some testcases based on other factors. I know the functionality to filter a test run specifically based on tags already exists, since it's available when I use it on a testsuite. I'd like to find a way to specifically use this functionality on a higher level when combining test suites in a regression, without enable/disable overwrites. Screenshot of the functionality for clarity.How to run only testcases with a specific tag, in a full regression.
My scenario is the following. I have a full regression with many test suites. In each of these test suites I have all my test cases tagged with "Known Defect" or "No defect" The idea was to be able to run the entire regression for only the known defects, and also for only the known working functionality. However when running my regression I seem to only be able to filter based on testsuite level tags, when running a testsuite seperately I can use testcase level tags but then I'd have to run every TestSuite seperately rather than in one large regression. Is there a way for me to run all these testsuites at once using testcase filters, or is this missing functionality from SoapUI pro? Thanks for your timeRe: Slow startup is back! v1.8.0
JKambli wrote: Try this, Download nightly build 64 bit and add these settings, https://support.smartbear.com/downloads/readyapi/nightly-builds/ In your Ready API installation folder, in the Contents directory, please find the vmoptions file and open it in a text editor. Add these lines to the file: Edit the vmoptions file in Ready API Pro installation folder\bin folder for windows and for Mac Applications/Ready-API-Home.app/Contents/ to accommodate following changes, Set Xms128m and -Xmx to 4000 if your ram is 4GB or 8000 if its 8GB -XX:MaxPermSize=128m -XX:MinHeapFreeRatio=40 -XX:MaxHeapFreeRatio=70 -Dsoapui.jxbrowser.disable=true -Dtest.history.disabled=true Once you do this, go to .readyapi folder in user folder > delete the contents of the db directory. Close and restart Ready API This worked for me to fix slow startup in v2.5.0 I know this is an old topic but it worked instantly, I think it was mainly because I had over 100MB of data in the db folder.JDBC driver is already registered log spam
I have a lot of JDBC steps and groovy steps that use a JDBC connection in my testing. Every time I make a JDBC connection it logs this in the ReadyAPI Log. This is making the log very hard to use and actually see the real errors because of how much this "error" is spammed. Does anyone know of a way to disable this logging? See example in the screenshot.
