jreutter
New Contributor
Joined 12 years ago
User Profile
User Widgets
Contributions
Provide touch actions for TC Desktop Module
We develop WPF applications for Desktop with touch screen. TC provides only mouse events of controls. Touch events and mouse events are entirely different beasts. They are not interchangeable. Testing of drag, flick, pinch, press+drag, rotate... (multi touch) are not possible to test with TestComplete. But this is neccessary.Re: Diff tool for Project Suite test run result Logs
I found a solution for us... (just an option for other stakeholders) Yesterday I've created a TestComplete script method to add a test item name and its result into a csv file. This method is called by the OnStopTest-Event for each test item and the current result is flagged by the OnLogError-Event. New test items will be appended to csv file (its result in the correct test run column), disabled test items which are already known in csv file, register a space. The csv file handling will be executed only when a entire test suite run is in progress (not if only a single test item is executed). csv file content example: Testrun ;TR1 ;TR2 ;TR3 ;TR4 ;TR5 TestItem1 ;passed ;passed ;failed ;passed ;passed TestItem2 ; ;failed ;passed ;passed ;passed TestItem3 ;passed ; ; ;passed ;failed TestItem4 ; ; ; ; ;passed ... At the beginning of a test suite run (or end) TC edits the csv file and adds " ;" to each line = existing but not executed test items are registered - and new results are separated in a new csv column After a test suite run is finished, I edit the csv file manually with conditional formatting rules, then it looks like the "NetSparker"-screenshot.Re: Diff tool for Project Suite test run result Logs
I cannot imagine exactly... Then I see how many TestItems failed (this is already comfortable), but not which TestItem result state changed. As I understand your request description, I need to filter the ProjectSuiteLog and click each TestItemLog to see its result history?Re: Diff tool for Project Suite test run result Logs
Yes, you're right. This is another reason why the TestComplete users should do the DIFF. They know when it makes sense. To have a meaningful test report e.g. after a regression test for Continuous Integration, the test suite run should be reproducible by its test coverage. I think, the danger is manageable to compare only the result of each single "Test Item" (new test, new error, fixed, skipped) without its TestItem-Content. The reason of a changed TestItem result, must be checked within the new/old TestComplete test log. (linked in the DIFF-Tool :smileywink: )Re: Diff tool for Project Suite test run result Logs
In our case, we don't use QAComplete. We also don't have a 'real TestManager', we work agil in small SCRUM-Teams. In my opinion the TestComplete responsible persons should be able to do the DIFF of test logs, because they create, change, execute and know the test cases and they can rank the new deviation of this 'list' (then commit this to their Testmanager or QAComplete)Diff tool for Project Suite test run result Logs
We use a nightly build and test environment with TestComplete. The ProjectSuite test run takes 12h and has a huge test result tree. It is pretty complex to compare the actual ProjectSuite test result with the prevenient test result, to see new divergences. It would be helpful to see new errors, fixed errors, new tests and not executed tests of a selected test result relating to a other selected test result.DLL interface handling TC6 vs. TC9
Currently we use TC6 and we evaluate if we upgrade to TC9. (TC6.51.405.5 <-> TC9.20.2460.7 Trial version) My environment is still the same. In TC6 following code works: sub test (dim all var) G_sAssistBasePath = "C:\Program Files\Motion Suite\CntStudio\" Set Def_DLL = DLL.DefineDLL("AssistBase") Set Lib = DLL.Load(G_sAssistBasePath + "AssistBase.dll") Def_DLL.DefineProc "ExecuteCmdLine", vt_lpstr, vt_lpstr, vt_int Def_DLL.DefineProc "GetErrorLine", vt_int, vt_lpstr, vt_int Set LpRet = DLL.New("LPWSTR", 1024) Set LpCmd = DLL.New("LPWSTR", 1024) LpCmd.Text = "NewAssist" bRet = Lib.ExecuteCmdLine(LpCmd, LpRet) end sub TC9 creates an exception during "Lib.ExecuteCmdLine(LpCmd, LpRet) " --> An exception occurred: 0xC0000005; class: ; description: '' Is there a change? Do I need to change something? ThanksReloading system variables
Hi, is it possible to reload the windows system environment variables to TestComplete (6.51.405.5). During a TC test run, i change some system variables (by WScript.Shell object for Win7, XP - Win32, x64). The new values are set on WinPC, but TC uses still the old values (in the sandbox??) System variables are set to TC after TC restart. I dont need to reboot the entire system via aqEnvironment.RebootAndContinue(). Ive tried to reload the system variables in several ways, but unsuccessful. Is there a simple way to reload in TC the windows system environment variables?
