ContributionsMost RecentMost LikesSolutionsRe: Ability to generate documentation from Test Suite / Case descriptions tuchka6215 - Who needs this feature and why? Warn readyapi users that their project is becoming too big Problem - I have learned on these forums and experienced that ReadyAPI projects can take several minutes (~15 minutes) to load when they become "too big". They also make the UI very sluggish. Impact - Projects load slowly, readyapi hangs during test execution and productivity is hampered. As a result, one might often kill task for readyapi which can potentially corrupt ReadyAPI or projects. Solution - Make readyapi warn users that their project is becoming too big. Perhaps by checking project size whenever ReadyAPI loads a project. PS - Unfortunately, most people don't read the docs/forums and many might not even get enough training. So, it is better to show this crucial limitation to users in ReadyAPI instead of keeping it buried in the forums or docs. The more frustrated people get, the more likely they are to blame the tool and explore other options instead of breaking down their projects. Feature request - Warn readyapi users that their project is becoming too big Problem - I have learned on these forums and experienced that ReadyAPI projects can take several minutes (~15 minutes) to load when they become "too big". They also make the UI very sluggish. Impact - Projects load slowly, readyapi hangs during test execution and productivity is hampered. As a result, one might often kill task for readyapi which can potentially corrupt ReadyAPI or projects. Solution - Make readyapi warn users that their project is becoming too big. Perhaps by checking project size whenever ReadyAPI loads a project. PS - Unfortunately, most people don't read the docs/forums and many might not even get enough training. So, it is better to show this crucial limitation to users in ReadyAPI instead of keeping it buried in the forums or docs. The more frustrated people get, the more likely they are to blame the tool and explore other options instead of breaking down their projects. SolvedRe: Big projects loading slowly - How to manage ? JKolosova - Thank you. That was helpful. Btw, can we reference other projects in workspace only with groovy or are there other ways also ? Re: Breaking up big projects into smaller and faster loading projects nmrao - Thanks for the reply. I appreciate your enthusiasm and all the effort you put into answering questions. But I wonder if there are too many details in this answer too soon. It would be helpful to first get an overview of which approaches or methods are possible. Then, I'd ask for the details about implementing them. So, I'll first try to understand which approaches you are suggesting. 1 - Create a template project with all the common functionality like getting auth token, creating user accounts etc. Copy this project to make your small projects. 2 - Create a Groovy or Java library with all the common functionality and use it in your small projects. Does this sound correct ? After that, we can get into the details like advantages/disadvantages and implementation details. Re: Run a test before other tests in a suite? I gave up on this and moved to other work. So, I'll close this thread. Breaking up big projects into smaller and faster loading projects I have seen some very large ReadyAPI projects which take about 15 minutes to load. It becomes a huge pain to load these projects 2-3 times each day. I would like to break them up into smaller projects so that they load faster i.e. in under 2 minutes. But, my concern is that I would have to repeat common functionality across all the pieces. Is it possible for one project to be able to use functionality inside another project? For example, Project-main can be broken into Project-1 to 5. All suites in project-main require common functionality like get login token, get some test data etc. Can I create a project Project-c which will have all the common functionality and then project-1 to 5 can use them? Or do I have to repeat the common functionality in project1-5? By the way, besides sharing common functionality, are there any other things I should note before I start breaking up a project into smaller projects ? Keywords - Sharing between projects, shared projects, common projects, refactoring projects, breaking up a big project, project loads slowly. PS - I have readyapi 3.0 and I simply cannot upgrade it for unknown reasons. SolvedRe: Big projects loading slowly - How to manage ? Another thing I'd like to add is that ReadyAPI takes too long (5-10 minutes) to open up when it has a too big project. If you want to make ReadyAPI at least open up quickly, then you can delete your profile settings and then run ReadyAPI. After that, you can load your project and this will take a lot of time. But, at least ReadyAPI opens up first. Deleting profile settings - 1. Go to C:\Users\YourUsername. 2. Delete default-soapui-workspace.xml. I often see too many ready api projects that are too big and can't be broken down. If you break the project down into smaller projects, then you'll have to replicate common things in each project like getting access tokens, deleting test data etc. which is horrible. I wonder if the Smart Bear team has a solution for this sonya_m. ReadyAPI - How to log all the inputs and outputs in proper order ? I have a test case which has only run test steps. These steps run "function tests" which can have REST & SOAP api calls, Groovy scripts and also SQL queries. Function tests meaning test cases which are disabled and used as utility functions. I would like to be able to view the inputs and outputs of each of the test steps in proper order, all in one document (MS word or text). It would be nice if the XML & JSON could be pretty formatted too. Can I do this easily with ReadyAPI? How? I need it so that I understand a big test at a quick glance. The ReadyAPI debugger is slow and confusing, so I want to avoid using it. SolvedHow to get database password in ReadyAPI? I have some JDBC tasks which have a working database connection. I want to connect to a database with a groovy script but cannot do it due to an authentication error. The connection string of the database has the username=OneDbUser and password = password_value. In the password field, the password field is hidden behind circles. I could not connect to the database with a groovy script or with the GUI client for the database. In both cases, I used the username and password given in the connection string. It looks like the password in connection string is different from the hidden password in the password field. So, how do I find out what is the actual password? How do I connect to a DB with a groovy script? Solved