ContributionsMost RecentMost LikesSolutionsRe: Generating Test Results for a Data Driven Test sas I moved to a different project and am working on a different arena now. However, I wasn't really able to get my output precisely on a PDF as I wanted to. But I had the output in an excel file. Generating the file was part of my Test Setup script . Unfortunately, I don't have code snippets to share with you. Thanks, SuperSingh Re: [Day 2/5] APIvsUI - Define what API testing / UI testing Is API Testing can be seen as a gate that ensures the application is behaving as intended & well within the scope of the requirements.The benefits of API includes broader scope of testing & early initiation of testing to identify bugs in the initial stages itself. The output will be a more cleaner & a product that adheres to the protocols & the requirements it is designed for. UI Testing plays a crucial role to Interaction & Customer friendliness . A poorly tested UI product will never last long irrespective of how well the application was developed or was tested at different stages prior to UI. UI Testing is the final impression that can make or break the deal. Bad UI leads to frustration & good UI enjoys appreciation from customers. Test Requirement Analysis, Test Plan/Strategy, Test Design, Traceability Matrix, Bug Tracking are some of the placeholders that play a crucial role in ensuring the quality of the application being tested & its adherence to the requirements. Coming to automation, it is a unit that every industry needs to survive in today's world. Planning test strategy in initial stages makes it easier to plan the scope of automation & how much of it is needed. Identifying the areas that can be automated is the key. Well defined scope for automation will not only enhance maximum coverage but helps focus on tests that need to be run manually. That's my opinion on API/UI Testing ! Cheers, SuperSingh Re: Accessing Test Case Property in Project's TearDown script Thanksnmrao &richie for your time. I was able to get the results with the help of your inputs. You guys rock ! Sorry for the delay in response. Cheers !!! - SuperSingh Re: How to write property value in setup script for test suiteS? Thank You ! That works :) Re: Set property at testsuite level access from all test cases Hinmrao How do you set a new property in Setup Script at TestSuite level ? say, I want to create a property "Counter" at Test Suite level via groovy. How do we do that? I tried the following but it doesn't work. testRunner.testSuite.setPropertyValue("Counter", "" ) Thanks, SuperSingh Re: How to write property value in setup script for test suiteS? I tried to set property at test suite level from Test Suite's SetUp script using the code you shared above. But that doesn't work. It throws the following error ERROR: com.eviware.soapui.support.scripting.ScriptException: Error in Setup Script of TestSuite Re: How to write property value in setup script for test suiteS? I tried to set property at test suite level from Test Suite's SetUp script using the code you shared above. But that doesn't work. It throws the following error ERROR: com.eviware.soapui.support.scripting.ScriptException: Error in Setup Script of TestSuite Re: Accessing Test Case Property in Project's TearDown script Hi richie Thanks for your time in giving the reply. The syntax you shared works when I put it individually. But I want to extract it from all the test cases. For e.g. if I have 5 testcases, I want to loop through all and extract the TCCount from their properties. The following piece of code doesn't work. But this is what I am looking to extract . testSuite.testCaseList.each { def name = "${it.name}" log.info name def tCCount = context.expand( '${'$name'#TCCount}' ) log.info tCCount } Thanks again for your time . Regards, SuperSingh Re: Error with access Excel using POI Hi, I was moved to a different project by the time this solution was provided. I will try to implement this & get back once I have an update. Thanks for your time ! Regards, SuperSingh Accessing Test Case Property in Project's TearDown script Hi All, I was looking for groovy script to access property from test cases in the TearDown script (of Project) On doing GetData simply returns " context.expand( '${#TestCase#TCCount}' )" [TCCount is the name of property] I have multiple testcases but GetData returns TestCasewhen I try to load using ReadyAPI feature. That's probably a bug in ReadyAPI I tried by providing testcase name in place of "TestCase" but it does not return anything. Can someone please provide an answer incase they have used this. Thanks ! Solved