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.
Report generated via teardown script does not contain any data
We need to be able to execute a security test and then save both the Security Issues Report and the Security Test Report with a specific filename structure to a network share. The test runner only allows directly saving a single report per test run.Therefore we need to generate these reports via a teardown script. Thankfully, or so we thought, SmartBear kindly provided a template for this exact thing (https://support.smartbear.com/readyapi/faq/configuring-readyapi-to-save-project-or-testsuite/) Modifying the script to target theSecurityTestCaseReport instead of the WsdlTestSuiteReport got the two reports generating upon the test finishing. However upon reviewing the reports, the Security Test Report was only populated with the number of test steps, number of security scans and the Start and End times areWed Dec 31 17:00:00 MST 1969 (which just happens to be the timezone adjusted epoch start ofJanuary 1st, 1970 at 00:00:00 UTC) - See attached pdfs Seeing as the sample script is fairly recent from4/30/2021, I decided to put the script directly in a TestSuite teardown script thinking maybe it only works with functional tests. No same issue no data in the report. Again to try and isolate anything odd about my projects, I used theVirtualServices-readyapi-project from the tutorials folder. Doing some searching of the community pages here, this issue has come up a few times with either no answer or recommending that people use the test runner or pointing people back to the teardown script linked at the start (circular dependencies are great eh) Does this teardown script actually work? Is it possible to generate reports from a teardown script? Can someone correct the script so that it does work? Regards Steve All of this was runningReadyAPI version 3.41.1
