Contributions
Older Browser compatibility for testing legacy applications in a ReadyAPI functional test
Hi, We are looking to use ReadyAPI to test some of our legacy applications. These applications often require to be run using an older version of a browser. Eg. IE 7.0. We have attempted to pass a user-agent header that is a compatible browser version to test the application however we are recieving an error on our application which states that an older browser version is required to use the application in the request response. This is the header we are passing: User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 10.0; WOW64; Trident/7.0; .NET4.0C; .NET4.0E; .NET CLR 2.0.50727; .NET CLR 3.0.30729; .NET CLR 3.5.30729; Zoom 3.6.0) Is emulating an older browser version something that is supported in a ReadyAPI functional test? And if so how can we go about implementing it. Many thanks, Kayleigh453Views0likes1CommentMasking encrypted properties in ReadyAPI Test for Azure DevOps task instead of plain text
Hi, The latest version of ReadyAPI 3.20.0 seems to fix encrypted properties being displayed as plain text in logs within the ReadyAPI software itself but this does not translate when running the project from Azure DevOps using the "ReadyAPI Test for Azure DevOps task" as encrypted properties are still being exposed there. 1. The project password for the task is in plain text - This property should be masked as anyone who views the task would be able to download and access the encrypted project and its properties. 2. Encrypted properties are displayed in the logs/requests as plain text The password has been encrypted in the custom properties using the "selected properties" project encryption . However, encyrpted properties are being shown in the task logs when a request that uses the properties fail or when logged using groovy script as plain text. This display of encrypted properties as plain text is unacceptable especially when creating production tests so it would be benefical if encyrpted properties are not exposed. Thanks, Kayleigh1.1KViews1like1CommentSOAP step timeout when running from Azure DevOps task
Hi all, We have a long running SOAP request which takes 5 minutes to respond.Our issue is when running this project within Azure DevOps using the ReadyAPI Test for Azure DevOps task it leads to a timeout.The task in Azure DevOps has a specified time out of 0 which is indicated as having an infinite timeout. However the task is failing after 2 minutes. Any advice would be appreciated. Thanks, KayleighSolved1.1KViews0likes2Comments