verycoolgreg
New Contributor
Joined 10 years ago
User Profile
User Widgets
Contributions
Add ability to stop custom script quickly and gracefully
Currently, if there is a custom Groovy script is running in soapUI Pro or ReadyAPI and it doing something complex, such as accessing some external APIs or resources, it is impossible to stop it in a reasonable amount of time. There is not 'Stop" button available either, so it ends up "hanging" the application. The only other way it would stop is by closing the ReadyAPI, but that's not only inconvenient but sometimes not advisable as it may not save the current project correctly.2.2KViews1like1CommentIntellisense + debugging capabilities for Selenium scripts
Now that ReadyAPI is supporting Selenium Webdriver, it would be really helpful to support development effort when building new testecases. Currently, when working with Selenium libraries, the editor feels more like a plain text notepad. Suggested improvement: Add IntelliSense and debugging capability during runtime, as it's extremely hard to find where the script is failing.1.2KViews0likes0CommentsAdd better oAuth mechanism built into the tool.
Nowadays, due to heightening security and data breaches, many companies are changing the authentication mechanisms to two-factor auth. Google, Amazon, Microsoft, GitHub, JIRA and more are on the two-factor authentication now. ReadyAPI does not have the ability to handle it. We need to have a way to deal with it via oAuth form the tool itself.2.2KViews1like1CommentHave ability to implement full blown Selenium framework
As it stands right now, ReadyAPI does have the support for the Selenium Webdriver and it does work to some extent. There is a way to build a reusable code by adding Groovy functions for the project by dropping the files in the /ext folder. Overall, the Selenium framework is much more complex and it has POM (page object model), data sources, and other things that make up a true, full-fledged framework. We need to have a ReadyAPI support to implement it as well as support the debugging capabilities/ IDE for it.825Views0likes0CommentsRe: SFTP/FTP TestStep
Hello Charles, I can definitely second your request as I had run into the same situation where I had to do an FTP upload. While we're waiting on the Smartbear to implement it, I have found a solution that you can use meanwhile. You could also make a Groovy file and add it to the /ext folder so that the FTP function globally available for the entire project. import org.apache.commons.net.ftp.* import java.io.InputStream import java.io.ByteArrayInputStream String ftphost = context.expand( '${#Project#ftphost}' ) //String ftphost = //"va-dev-dmstable.alterian.com" String ftpuser = context.expand( '${#Project#username}' ) String ftppwd = context.expand( '${#Project#password}' ) int ftpport = 21 def newDropFolderCategoryName = context.expand( '${DM FTP Drop Folders - Create Drop Folder Category#newDropFolderCategoryName}' ) def newImportDropFolderName = context.expand( '${DM FTP Drop Folders - Create Drop Folder Category#newImportDropFolderName}' ) String ftpDir = "/${newDropFolderCategoryName}/${newImportDropFolderName}" int TENSECONDS = 10*1000 int THIRTYSECONDS = 30*1000 //Declare FTP client FTPClient ftp = new FTPClient() try { ftp.setConnectTimeout(TENSECONDS) ftp.setDefaultTimeout(TENSECONDS) ftp.connect(ftphost, ftpport) //30 seconds to log on. Also 30 seconds to change to working directory. ftp.setSoTimeout(THIRTYSECONDS) def reply = ftp.getReplyCode() if (!FTPReply.isPositiveCompletion(reply)) { throw new Exception("Unable to connect to FTP server") } if (!ftp.login(ftpuser, ftppwd)) { throw new Exception("Unable to login to FTP server") } if (!ftp.changeWorkingDirectory(ftpDir)) { throw new Exception("Unable to change working directory on FTP server") } //Change the timeout here for a large file transfer that will take over 30 seconds //ftp.setSoTimeout(THIRTYSECONDS); ftp.setFileType(FTPClient.ASCII_FILE_TYPE) ftp.enterLocalPassiveMode() // String filetxt = "Some String file content" // InputStream is = new ByteArrayInputStream(filetxt.getBytes('US-ASCII')) String filename = "C:\\QA_Automation_Branch\\DataFiles\\email_list_test_file_15_records_FTP.csv"; is = new FileInputStream(filename); try { if (!ftp.storeFile("email_list_test_file_15_records_FTP.csv", is)) { throw new Exception("Unable to write file to FTP server") } //Make sure to always close the inputStream } finally { is.close() } } catch(Exception e) { //handle exceptions here by logging or auditing } finally { //if the IO is timed out or force disconnected, exceptions may be thrown when trying to logout/disconnect try { //10 seconds to log off. Also 10 seconds to disconnect. ftp.setSoTimeout(TENSECONDS); ftp.logout(); //depending on the state of the server the .logout() may throw an exception, //we want to ensure complete disconnect. } catch(Exception innerException) { //You potentially just want to log that there was a logout exception. } finally { //Make sure to always disconnect. If not, there is a chance you will leave hanging sockects ftp.disconnect(); } } return true9.6KViews0likes0CommentsRe: Run SOAP UI PRO Tests via Jenkins
Also, I have a few tips for all who are trying to run ReadyAPI scripts from Hudson/Jenkins. In Jenkins, there is an option to produce JUnit type of report. It comes very handily when we would like to see the results of the test run. You could also setup Slack (collaboration tool ) with Jenkins and see the test results via slackbot notifications. Integration of SOAPUI and Hudson/Jenkins For integration, we have to consider following requirements and same will be used to decide integration style. Requirements: SOAPUI should be run from Hudson Generate reports in JUnit style and incorporate with Hudson. Show logs in console output. Run any project with different global properties of SOAPUI 1. SOAPUI should be run from Hudson Hudson have good feature of execution of batch of commands of windows and Linux and SOAPUI is providing test runner of its own, we can run SOAPUI from Hudson easily. We can run it as same way as we can run soapui from command line. So it can be integrated easily and using Hudson we can view console output as well. For this first create a new job in Hudson. This link will help you understanding the Hudson management; http://www.solitarygeek.com/java/hudson-ci-server-a-step-by-step-guide-part-i/ After creating a job, go to configure section of the job and “Add build step” to run shell script / batch file as below to run SOAPUI from Hudson . 2. Generate reports in JUnit style and incorporate with Hudson Hudson have inbuilt functionality of digesting JUnit style report and SOAPUI generates reports in JUnit style and Hudson generates good trending and result reports based on it. To enable JUnit style report in Hudson we have to select “Publish JUnit test result report” option and it will ask for JUnit style report xml file path. If you are creating different JUnit style report in different folder than give that path using wild cards and Hudson will check for all the JUnit style report and will show the consolidated results and trends. The path should be relative to WORKSPACE. 3. Show logs in console output As described in point-1, it is necessary to have log information handy for test and Hudson have special area to show console output. 4. Run any project with different global properties of SOAPUI To make our test dynamic, it is must that our tools supports run time property setup option and SOAPUI command line runner supports this via global properties. Because we can setup global properties values during run time and which we can use to achieve dynamic nature of our test framework and as we know Hudson support execution of tool through command line or shell scripting. For example, I want to run SOA test daily after nightly build of my application. Here we are assuming that our SOAUI test project is available in SVN and application source is also available in SVN. So for this the steps for setting up job will be as below: Create one new job in Hudson for building the code. Configure SVN from which we have to download the latest source of application. Configure build steps like ant script or batch file or shell script. Configure schedule to run the job daily. Save job. Create one more new job in Hudson for testing the build which was setup in previous step. Configure SVN path to get latest test project from SVN. Configure the batch commands to invoke and run the soapui tests. Set build job as triggering job to start this test job. Set email address to whom we want to send the test report. Save the job. Now the source build job will start at scheduled time and completion of build it will start the test job. Conclusion There are many options in Hudson and SOAPUI to achieve maximum flexibility of building and testing the jobs and apart from this we have integrated functional UI testing with Hudson.4.3KViews1like1CommentRe: why do i have to reset my password each time I visit the SmartBear forum?
Thank you all for your responses here. I have discovered one more issue and came up with the solution. The issue: Even after resetting the password via the "forgot password" link, I could not log into the community site. Solution: Open a brand new browser window in Incognito mode ( Chrome/Firefox), then copy your link from the reset password email into the browser address bar. Complete the reset flow and now you'll be able to login to the site. Note: I believe LastPass still has an issue if you try to go through reset password with it.8.5KViews2likes0Comments