Kazuka
New Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
Best Practice for permanent availability
Hi all, At the moment i have to test a web application. Since we are working in DevOps, my tests should run everytime a pull request to stage environment is performed. i already have some experience with testing desktop applications, there i start my tests from devops manually and this works fine every time. as i wanna get more into automating the automation my question would be on how to create the ideal setup for this task? whenever i started my desktop test and closed or minimized the remote session (manually, energy options, ..) TestExecute could not interact with the GUI anymore and the task bricked. my first idea was to set up a physical test machine that runs 24/7. but as this does counterfeit the idea of green it im looking for a better solution. maybe some of you had the same challenge, if you did please let me know. i already tried the solution with a permanent remote session by disconnection via batch. problem i had was that all dialogues were maximized. thank you very much in advance! KazuSolved738Views0likes1CommentRe: Executing a Project from Azure DevOps resets Project Variables
Hi & thank you all for your help so far! I just realized i used Temporary Variables instead of Persistent Variables, as i said my first time working with these, i will try this suggestion from hkim5, i am positive this will fix the issue! Thank you very much & have a nice day!1.4KViews2likes0CommentsExecuting a Project from Azure DevOps resets Project Variables
Hello SmartBear Community, My current project is testing a shopping cart. Therefore i created a new TestComplete Project Suite and added one Project. The flow is as following - one ore more KeyWord Tests each: - Open the Browser and Navigate to the User Selection for Edition and License Amount - Select a Edition and enter a RNG Amount of Licenses - Put the Amount of Licenses and the calculated Price each into a String Variable ("Transfer Variable" from one page to the next) - Compare the Amount of Licenses and the calculated Price from the Variables with the ones shown in the Shopping Cart Whilst this flow works flawless on my local System when i start the Project / Project Suite, starting it via Azure DevOps DISCARDS the Project Variables between the KeyWord Test since the Assemblies are not loaded as whole project but one KeyWord Test after another. I logged each step so i can 100% confirm the variables are discarded after the KeyWord Test is done. That is my first time working with Project Variables in DevOps, all other DevOps Tests work flawless so far. Did anyone already experience that same challenge and how did you fix it? Update: Using ProjectSuite Variables instead of Project Variables bears the same issue. Thank you very much in Advance & Best Regards MichaelSolved