| Re: [ease-dev] Tooltip testing |
Hi Christian,
Yes. These are the methods that I have been trying to test. Every time these 3 methods are called, the workbench is loaded to generate the URL. As the first approach I sub classed the ModuleDefinition class and created a customized ModuleDefinition object and passed it to getMethodHelpTip() method. But the build failed in Hudson due to workbench problem. But this test ran successfully in my local machine.
However I can give a try to rewrite the test by creating a simple module and a help page. But I have to do something about the workbench problem.
Thank you.On Fri, Feb 19, 2016 at 5:30 AM, Christian Pontesegger <christian.pontesegger@xxxxxx> wrote:_______________________________________________Hi,
ModuleHelp has 3 public methods, these are the methods you should test. Do not change the base class, it is not needed. If you are not able to run the workbench and therefore the help system on Hudson, then lets forget about these tests. Did you already give it a try?
Christian
Am 17.02.2016 um 18:55 schrieb Vidura Mudalige:
Hi Christian,
Thanks for the detailed guidelines.:) I will try this approach.
Writing the test without changing ModuleHelp is somewhat problematic. What ModuleHelp currently do is after passing a ModuleDefinition object, get the help page location from the object and generate the URL of the page using the location. After that, parse the html page to get the relevant help content and return the relevant help content as a string. Every time it requires to load the workbench to generate the URL of a help page.
ease-dev mailing list
ease-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ease-dev--Vidura MudaligeUndergraduateComputer Science & EngineeringUniversity of Moratuwa.