Design For Automated testing of a Grid template UI usnig ReadyAPI
##URGENT### Hi Guys, My team is looking to automate our application Grid Based Application. I am very new to automation and the requirement is to build a test-suite in ReadyAPI . The Requirement is to validate the Stored Procs/ Various services that run behind to generate data and validate it against a query that gets the same data using query . As a QA i have very minimal knowledge of SQL and to be able to do something requires a humongous effort . Question : Can someone please help suggest any framework design in mind for such validation or any other ideas for example if we could take the data from the website and validate it against the query would it make sense . Please suggest and share your expertise .
encoding of utf-8 is set for some APIs test cases and not for some in project properties
Hi mates, I am sending unicode characters in Json request payload. The server is returning "NO success" response. But If I add encoding as UTF-8 in that test case(REST) properties, response comes as "SUCCESS". Is it the the right thing to send UTF-8 explicitly ? And if yes, how does this will be addressed when any integrations call that API ? And, I could see some other APIs test cases shows UTF-8 as encoding by default in ReadyAPI. So, not sure whats going on. Appreciate any help. Thanks. Ravi.
Github Action Test Reporter to Export Test Results to GitHub
Using GitHub-hosted runners on windows, running ReadyAPI testrunner in github action as: jobs: runReadyAPITest: runs-on: hosted-runner-name steps: - name: Run ReadyAPI Test run: | echo "Running ABC Test" & "C:\Program Files\SmartBear\ReadyAPI-3.10.1\bin\testrunner.bat" C:\Path\To\ReadyAPI\Project\ -fC:\Path\To\Save\Test\Result "-RProject Report" -FXML - name: Publish ReadyAPI Test uses: mikepenz/action-junit-report@v3 with: report_paths: '**/Path/To/Saved/Test/Result/XML_REPORT_NAME.xml' Test is running as expected and report XML is created. Now trying to pull the XML report in Github and facing issue with that. Tried following Github actions 1. https://github.com/marketplace/actions/junit-report-action 2. https://github.com/marketplace/actions/test-reporter Getting different errors with different ways to generate XML report. Used "-RProject Report", "-RTest Suite Report" and "-RData Export" to generate different XML reports and used them with above actions to display test results in github UI but it's not able to pull and show the test results in github UI With "-RData Export" option in testrunner command and with dorny/test-reporter@v1 action (reporter attribute value java-junit), error is Cannot read property '$' of undefined With "-RData Export" option in testrunner command and with dorny/test-reporter@v1 action (reporter attribute value jest-junit), error is Cannot read property 'testsuite' of undefined For various XML reports, With mikepenz/action-junit-report@v3 action, it says No test results found! If you could help on how can we pull test results and display in github UI. Can provide more details on errors if needed.ReadyAPI and TestEngine with Zephyr Scale
In this post, we are going to talk about using some of the SmartBear API testing tools and writing the results in an automated fashion to Zephyr Scale. But first let's take a step back and discuss a general approach of using testing tools with test management tools. At a manual level, when creating simple Multi-Protocol API tests, we might use a lighter weight tool like SoapUI Open Source, a great tool for quick and basic functional and performance API tests. After we trigger the test manually, we as humans would parse the report for any details on the test run, and to track it would update a spreadsheet, testcase in Jira, but somewhere. This sequence is important to note for when we start to advance to an automated workflow. Now let's talk about automating this process. We execute our API tests in an ephemeral environment, publish the results to a relative location, and then pass those results from that relative location to a test management platform. It is quite simple. In this workflow it tends to be easier to use a tool that has native integrations into CI platforms like Jenkins and Azure Dev Ops, that make managing our executions in these ephemeral environments much easier. Here, ReadyAPI, or TestEngine is the clear choice as they both seamlessly integrate into any CI-CD system and have native integrations into Jenkins, Azure, and many more. Now that sequence I mentioned earlier is very important. We will execute our API tests, and then pass the results into Zephyr Scale as step 2 in the pipeline. Here is a look at a scripted pipeline approach, note that there is freestyle job options available in Jenkins too. ReadyAPI Jenkins Plugin: https://support.smartbear.com/readyapi/docs/integrations/jenkins.html TestEngine Jenkins Plugin: https://support.smartbear.com/testengine/docs/admin/jenkins.html node { stage('Run API Tests') { // Run the API Tests using ReadyAPI or TestEngine stage('Pass Results') { //Pass Results to Zephyr Scale } } Now we need to be a little more specific with the 'Run API Tests' Stage. Above I mention when we run our API Tests in an automated fashion, we need to write the results to a relative location so that we can then send those results to Zephyr Scale from that location. Both ReadyAPI and TestEngine allow us to write results to locations as part of the command-line or native integrations. I will show command- line options for ReadyAPI and UI native integration for TestEngine but both options are available for both tools. Starting with ReadyAPI, testrunner CLI, the -f and -F flags represent the directory we are writing to, and the report format, respectively. ReadyAPI offers reports in PDF, XLS, HTML, RTF, CSV, TXT and XML, but the automation recommendation would be to pass results in the Junit-XML option. At a basic level we need this: testrunner.bat [optional-arguments] <test-project> And we need to specify -f and -F testrunner.bat -f<directory> -F<args> <test-project> and with -f requiring a relative directory, that can change based on the CI system. I will use Azure Dev Ops for both my examples here. In Azure I pull my test cases from the $(System.DefaultWorkingDirectory), which contains my git repo. In Azure I publish results to the $(Common.TestResultsDirectory) An example full command would look like this: "C:\Program Files\SmartBear\ReadyAPI-3.40.1\bin\testrunner.bat" -r -a -j -f$(Common.TestResultsDirectory) "-RJUnit-Style HTML Report" -FXML "-EDefault environment" "$(System.DefaultWorkingDirectory)/" With TestEngine it's very similar, but I am highlighting it through the native integration, note the publish test results and save Junit report option enabled below: Now lastly, we need to send the results to Zephyr Scale from the pipeline, before our release is over. I think it's easiest with the Zephyr Scale API: https://support.smartbear.com/zephyr-squad-cloud/docs/api/index.html along with the Auto-Create Test Case option to true. The command below is a basic example, and replica of the one seen in the Azure Pipeline screenshot. curl -H "Authorization: Bearer Zephyr-Scale-Token-Here" -F file= Relative-Location-of-Report-Here\report.xml;type=application/xml "https://api.zephyrscale.smartbear.com/v2/automations/executions/junit?projectKey=Project-Key-Here&autoCreateTestCases=true" After you modify the API token, Relative location, and project key you are good to run the pipeline. When we jump to Jira, we can see inside Zephyr Scale that the results are populating. Even with transactional Data on the failed test steps
