Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [ease-dev] Tooltip testing
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.

On Wed, Feb 17, 2016 at 3:08 PM, <Christian.Pontesegger@xxxxxxxxxxxx> wrote:

Hi Vidura,

 

as posted before this test shall not run during our integration tests as it will definitely fail.

What you could do to test it thoroughly would be to create a simple module in our test fragment, register it correctly like a normal module. Create documentation for this test module manually and add it to the commit. This way your test could access a given module which already comes with documentation. You also know which documentation text to expect as the docs are part of your test fragment.

On the build server tests are run as plugin tests without UI. So I am not fully sure if the help server will be available, but you could give it a try.

 

Changing ModuleHelp just to create a testcase is not the ideal approach. Best try the approach above

 

Best regards

Christian

 

From: ease-dev-bounces@xxxxxxxxxxx [mailto:ease-dev-bounces@xxxxxxxxxxx] On Behalf Of Vidura Mudalige
Sent: Wednesday, February 17, 2016 10:30 AM
To: ease developer discussions
Subject: Re: [ease-dev] Tooltip testing

 

Hi Christian,

I had given the Plug-in Project root folder incorrectly. I fixed it and now I can generate help pages without a problem.:)

I can run the test using the help page of the environment module. Since the environment module is not belong to the ModuleDefinition type, I had to modify the ModuleHelp.java class to handle the EnvironmentModule type.

The test will fail during the gerrit build since the code uses the workbench to get the URL of the help system. But I can comment the test and commit. Shall I commit?

Thank you.

 

On Wed, Feb 17, 2016 at 1:46 AM, Christian Pontesegger <christian.pontesegger@xxxxxx> wrote:

Hi Vidura,

regarding 1) are you able to run the default javadoc doclet? If yes then also this doclet should do. The workspace will not refresh automatically by default, so I guess you have to manually refresh the project. Did you add the "-root ..." parameter on the 2nd page of the javadoc wizard page?

2) Yes, you will need to run a plugin unit test to access help. The problem with this approach will be that there are no help pages available when you run your tests on the integration server. So I guess while this might be a local test we will not be able to run it during an automatic build.


regards
Christian
_______________________________________________
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 Mudalige

Undergraduate

Computer Science & Engineering

University of Moratuwa.


_______________________________________________
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 Mudalige
Undergraduate
Computer Science & Engineering
University of Moratuwa.

Back to the top