felipefigueired
Occasional Contributor
Joined 8 years ago
User Profile
User Widgets
Contributions
Re: Failure Print's Log Scripts Function - TestComplete 12
Robert, I got it sorted out. According to your point about logic, I've reviewed all the code. In the moment of capture the size and location of the program was coming dirt with incorrect values. By clearing and firing the "refresh command" (Aliases.Corporate.Refresh ()) on the controls, it captured the size and location correct. Now the Print Screen Command again only work on the system and even with 2 monitors. Thank you very much for the help and analysis. Felipe Figueiredo4.3KViews0likes0CommentsRe: Failure Print's Log Scripts Function - TestComplete 12
In the annex follows the definition of Integer type variables in the project. They are fed at the start of execution, after the system is opened. // Check Corporate Location on Desktop Project.Variables.DesktopX = Aliases.Corporate.DXProgramMainForm.DesktopLocation.X; Project.Variables.DesktopY = Aliases.Corporate.DXProgramMainForm.DesktopLocation.Y; // Verify height / width of Corporate Project.Variables.CorporateWidth = Aliases.Corporate.DXProgramMainForm.Size.Width; Project.Variables.CorporateHeight = Aliases.Corporate.DXProgramMainForm.Size.Height; I used the "Debug" and the "Whatch List" to analyze the variables, and they are correct with the values. I just ran the test with Sys.Desktop and it showed error. With Sys.Desktop.Picture () the print screen does correctly, but with the entire Desktop image (attachment). As for using multiple monitors, here at the company we use at least 2 because we perform various tasks and a larger Desktop is required to follow some processes. The problem is that these logs are very heavy if the entire screen print screen is made. We used this way 1 year in version 10.4.3KViews0likes0CommentsRe: Failure Print's Log Scripts Function - TestComplete 12
Follows a snippet of code Indicator.PushText("Verificando se existe msg XtraMessageBoxForm"); if( Aliases.Corporate.WaitWindow("*", "JBS Corporate",-1,100).Exists || Aliases.Corporate.WaitWindow("*", "Erro",-1,100).Exists ) { Options.Run.Timeout = TimeoutValue; Log.Error('Erro exibido na tela associado a alguma regra. Verificar.','', pmNormal, undefined, Sys.Desktop.Picture(Project.Variables.DesktopX,Project.Variables.DesktopY,Project.Variables.CorporateWidth,Project.Variables.CorporateHeight), -1); Aliases.Corporate.WinFormsObject("XtraMessageBoxForm", "*").WinFormsObject("SimpleButton", "*").ClickButton(); return false; }4.3KViews0likes0CommentsRe: Failure Print's Log Scripts Function - TestComplete 12
Robert Thanks for the contact, Yes, the purpose is to print the error message and inform the log according to the Picture function. As for logic, I do not think it's the problem, because it's just a log that besides the message, it captures the image according to the parameters (Desktop X, Y, Width and Height of the System). These 4 parameters are captured at the beginning of the system opening and added in global variables to be used in all scripts. This function was normally used in version 10 of TestExecute / TestComplete, however when migrating to version 12 it is not working.4.3KViews0likes1CommentFailure Print's Log Scripts Function - TestComplete 12
“We are having a problem in the version of TestComplete / TestExecute version 12. We have a SmokeTest script that performs several tests on the system screens every day. If the system displays a failure message, the script performs a Print Screen according to the function below to get only the system image, because we use at least 2 monitors and, however, from the migration this function no longer works. Can help us, please? Analyzes carried out: - Analysis of the logic, variables and types of variables; - Function call analysis; - Analysis of Windows updates. The machine did not receive updates after August / 2016 and even updating remained; - Analysis of the versions of Windows 7 and 8; - Isolated function test; - Test the same code with version 10 of TestExecute / TestComplete successfully; - Analyze and Test with Antivirus and without Kaspersky Anti-Virus. - Analysis of project properties. - Analysis of the X, Y location in the System Desktop and analysis of the Height, System Width; - Uninstalling SmartBear software and reinstalling; - Formatting the machine.”Solved4.5KViews0likes8Comments