Difference between revisions of "GXtest Designer Troubleshooting"
From GXtest Wiki
(→Importar Test Cases grabados) |
(→Ejecución) |
||
| Line 10: | Line 10: | ||
:If the name of a control is longer than the maximum supported by GeneXus, in the generated HTML the name appears shorter, so, there is certain inaccuracy at the moment of identify the GeneXus control assosiated with the HTML control, and for this reason a warning message appears to verify if the element is the correct one. | :If the name of a control is longer than the maximum supported by GeneXus, in the generated HTML the name appears shorter, so, there is certain inaccuracy at the moment of identify the GeneXus control assosiated with the HTML control, and for this reason a warning message appears to verify if the element is the correct one. | ||
| − | == | + | == Ejecution == |
| − | ; | + | ;Two different windows of Internet Explorer appear, one in about<nowiki>:blank</nowiki> and the other one in the site under test, but it doesn't start playing |
| − | : | + | :This problem is present in Internet Explorer 7 (under Windows Vista), with the Beta version of GXtest Designer. The problem happen because the site should be under the same Security Zone of about:blank (both in the Intranet Zone for example) and this security zone must have the protected mode unactivated. See [[How to adjust the Security zone to the test site]]. |
;There is no Opened Browser | ;There is no Opened Browser | ||
| − | + | ¿Is Firefox the default browser? | |
| − | :GXtest | + | :GXtest cannot communicate with FireFox if it is not using JSSH (plugin required to automate). |
| − | : | + | :Workarounds: |
| − | :- | + | :- Use a browser previously openned by GXtest |
| − | :- | + | :- Use the browser with JSSH. In order to do that execute from the command line the following command: |
firefox -P testyard -jssh | firefox -P testyard -jssh | ||
| − | :( | + | :(You could change the FireFox shorcut in order to open it always that way.) |
| − | + | ||
== Licencias == | == Licencias == | ||
Revision as of 18:07, 17 December 2010
Contents |
Import KB
- Trying to import a KB into GXtest and then an error message appears
- "Method not found ..."
- This error ocurrs if you don't have installed the Microsoft Framework .NET 2.0 Service Pack (SP1)
- You can download it from here: Download .NET 2.0 SP1
Import recordered Test Cases
- The name of the control XXX is too long
- If the name of a control is longer than the maximum supported by GeneXus, in the generated HTML the name appears shorter, so, there is certain inaccuracy at the moment of identify the GeneXus control assosiated with the HTML control, and for this reason a warning message appears to verify if the element is the correct one.
Ejecution
- Two different windows of Internet Explorer appear, one in about:blank and the other one in the site under test, but it doesn't start playing
- This problem is present in Internet Explorer 7 (under Windows Vista), with the Beta version of GXtest Designer. The problem happen because the site should be under the same Security Zone of about:blank (both in the Intranet Zone for example) and this security zone must have the protected mode unactivated. See How to adjust the Security zone to the test site.
- There is no Opened Browser
¿Is Firefox the default browser?
- GXtest cannot communicate with FireFox if it is not using JSSH (plugin required to automate).
- Workarounds:
- - Use a browser previously openned by GXtest
- - Use the browser with JSSH. In order to do that execute from the command line the following command:
firefox -P testyard -jssh
- (You could change the FireFox shorcut in order to open it always that way.)
Licencias
- El License Manager no me muestra los productos GXtest Designer ni Manager
Para que le aparezca en la lista tiene que estar en el Registry:
[HKEY_LOCAL_MACHINE\SOFTWARE\ARTech\GeneXus Authorizer\Product Description] Name_98_10=GXtest Designer (X) Name_99_10=GXtest Manager (X)
Si no aparece es necesario ejecutar el archivo prodgxtest.reg que está en la carpeta de instalación de GXtest.
También en los filtros del gxlmgr.ini tiene que estar habilitado:
[Filters] Version = -1 Product62 = 10 (9 para la beta) Product63 = 10 (9 para la beta)
A menos que en el ini no tenga esa parte de los filters.
