ContributionsMost RecentMost LikesSolutionsRe: How to start chrome in incognito from keyword test AlexKarasThankyou for the addition, I think that is a quite valueble addition which I hadn't thought of yet. The only problem here for me is, that the function tristaanogre described indeed seemed to be enabled in chrome, but it didn't prefill any field with any value. At least as far as I could see it were always just empty textfields and there was no possible value given. That's why I asked how one could start the incognito modus, so that I at least know that I am not messing with an older build of the page or whatever. At this moment I don't care about the prefilling. It should not prefill and all I want to know at first is that the page is working normally when you get there for the first time. Re: How to start chrome in incognito from keyword test Where is the answer that tells us how to open chrome incognito modus from a keyword test? Or just always when testcomplete is executing its tests? I am frustrated with chrome not having the ability to throw everything it knows away when you close it. At this moment I have the feeling it is messing with me with a test, because it doesn't throw away everything. So I want to have a clean browser when starting my test. How do I do this? Chrome is the only browser that is messed up at the moment. When I execute this test in non-incognito modus it fails, when I test it in incognito modus, it doesn't fail. So please tell me how to start chrome incognito via testcomplete. computer gets locked while executing specific keyword test with Testcomplete Yesterday I was making a keyword test which would go from a login page, to a forgot password page. Everytime I execute this test (with testcomplete on win 10), for every browser, when I click on the "forgot password" link, my computer gets locked. When I execute this test manually it doesn't lock my PC. Has anyone ever had this problem before? And is this behaviour that should be expected when your application is "really safe"? Or might there be something else going wrong? I have added a screenshot of the test. I have not found the cause of this problem, but the problem seems to be solved when I restarted the PC which was running Testcomplete. Re: computer gets locked while executing specific keyword test with Testcomplete Thank you for all the replies. I am sure that I did not use a win+l key combination in my test. The test had been running for a few seconds, maybe a minute and then it gets locked. So I cannot imagine that it would be the windows machine locking because of idlenes. Also because that feature should be disabled (but in Windows you never know ofcourse). I was not trying to logon to remote desktop via testcomplete, I was already logged on via remote desktop and there the test was executed, which was just testing a webpage, nothing more. The weird thing is: I have logged on via a different way and restarted the computer.. and now.. it seems to work normally again. As in, when I execute this test now, my computer is not getting locked. Therefore I think I might blame Windows.. but ofcourse, you can never be sure. Re: check font in Test complete It seems to be, that the provided solution indeed only checks if the font is correct in the code, but it doesn't verify that the font visible is the correct one. Which was exactly the thing I wanted to check. Might it be the case that I'm not looking in the correct place, or would we indeed need some graphical check? If we need a graphical check, what would be the best way to do this? I do get errors in the console that the font cannot be loaded, but I can't imagine this would be the only way to check. I have used the code of AlexKaras his link to another thread and modified it a bit. With that code, I get a property back with a value I expect. But It always gives this value, even when it wasn't possible to load the font. function getCSSProperty(element, prop){ var style; style = Aliases.browser.Page('*').contentDocument.defaultView.getComputedStyle(element, ''); return style.getPropertyValue(prop); } function checkCSSProperty(element, prop, checkValue){ var testValue; testValue = getCSSProperty(element, prop); testValueArray = testValue.split(','); testValue = testValueArray[0]; testValue = testValue.trim(); if (checkValue.indexOf(testValue) >= 0) { Log.Checkpoint(prop + ' has value of ' + checkValue); } else { Log.Error(prop + ' value of ' + testValue + ' does not match ' + checkValue); } } Re: computer gets locked while executing specific keyword test with Testcomplete When I click on that link, I will be redirected to a new page in the same browser. There are no models or whatsoever involved. When I execute this test manually, that is what happens. But when executed via Testcomplete it locks my computer as in I need to enter my windows password again, so that would be the lock screen indeed. Because of this, testcomplete cannot continue with its test, unless I unlock the computer again. This is only on the windows 10 pc where I logon via remote desktop btw. Re: check font in Test complete Thanks for the idea Alex! But than what would be the property to check? Or how do I know which property to check and what kind of element should it be? check font in Test complete I am searching for a simple way to check if the font of a webpage is correct. We have been playing with fonts several times and I have seen that not all browsers are able to find the font. So I would like to add this in my testcase, but I have not found a way to do this yet. Give the option to use 24-hour time format QA-complete We are not used to use the am/pm notation and I keep getting confused if my scheduled tests will be run in the morning, or afternoon. So I would like to have an option that the 24 hour notation is used everywhere. Re: Call shared steps within a test and at execution, include the detail of the shared steps. Why doesn't this feature have the status "implemented" yet? To me it feels like the ability to add a keyword or script routine to the test you are working on, is already the solution for the question here.