Missing docs for installing into an existing FitNesse installation

Question

Missing docs for installing into an existing FitNesse installation

MMatten opened this issue 7 years ago · 26 comments

Hi.

(Is there a more appropriate support forum?)

I can't find any docs about how to install just the fixtures into an existing FitNesse installation. E.g. so I can combine web service testing with existing database testing assets.

Is this possible / feasible / etc?

Answer 1 · 2018-01-31T05:54:33.000Z

You are right there is no documentation on that. I wouldn't know what to put in it, since it really depends on what your existing installation looks like.
To be frank, what I've done in the past is create a new project based on the archetype/sample project and copy existing installation's code and wiki pages to that. But I see no reason the other way around can not be done.

As far as I can tell there are a couple of elements you could incorporate, and you can choose to do just one or all.

Include the hsac-fitnesse-plugin to your plugins folder: for extra slim tables and symbols
Include the hsac-fitnesse-fixtures (and its dependencies) to your classpath: to be able to use the fixtures themselve
Include the selenium web drivers to a new webdrivers directory in your wiki: to use Selenium without having to set system properties using Selenium: only when SeleniumDriverSetup is used

Answer 2 · 2018-01-31T09:27:51.000Z

Thanks for the response. My current installation is based upon the DbFit distribution (https://github.com/dbfit/dbfit) as I'm going mainly database / data warehouse testing and I wanted to add web services (mainly SOAP) testing for the services that sit over a database layer.

The DbFit distro (https://github.com/dbfit/dbfit/releases/tag/v3.2.0) uses a stock FitNesse build (pulled from the Maven central repo). The current released version is from a couple of years ago (a new release will be out very soon using the latest FitNesse release).

I'll try transplanting in the above items to my installation and see where I get to and report back!

Answer 3 · 2018-01-31T10:20:15.000Z

I seem to hit the following error whichever way I try to set things up.

Do you know what might be going wrong?

Answer 4 · 2018-01-31T10:35:02.000Z

Try clicking the 'Execution Log' button. That page might have more info

Answer 5 · 2018-01-31T10:43:58.000Z

No clues. I can see your fixtures should be getting picked up though.

Answer 6 · 2018-01-31T10:44:27.000Z

I'm now using the latest FitNesse build for this installation.

Answer 7 · 2018-01-31T11:03:20.000Z

and the console where started fitnesse. Does that show anything?

Did you copy all dependencies for my fixtures to your installation (either in lib or fixtures)? (All the jars packaged in my -standalone.zip's fixtures directory.)

Answer 8 · 2018-01-31T13:18:05.000Z

Thanks again.

I did add all the JARs from your distro to the fixtures folder. You can see they get picked up:-

Here's the test page again:-

Here's the console window:-

Answer 9 · 2018-01-31T13:26:43.000Z

Note that I've also updated my plugins.properties to add the content from your distro. I'm not really sure if I needed to.

Answer 10 · 2018-01-31T13:54:59.000Z

The plugins.properties change is only needed if you add the maven classpath plugin (which I would not recommend for you).

I just thought of what you might have missed. The actual fixture classes (or would that just be something that would happen to me?) :-)

Try placing the .jar in the fixtures directory...

Answer 11 · 2018-01-31T14:45:28.000Z

I've got all the class files installed. E.g. under fixtures/nl/hsac/fitnesse/fixture/slim I can see lots of .class files.

All your .jar files are in the fixtures folder.

I don't think I need any custom .jar files for this example test.

Answer 12 · 2018-01-31T14:54:03.000Z

For the file hsac-fitnesse-fixtures-3.16.0.jar I take it this is the archive/artefact that's the same as the .class files I've already got installed. Is this right?

Answer 13 · 2018-01-31T14:59:23.000Z

Yes you are right

Answer 14 · 2018-01-31T15:01:24.000Z

But in the screenshot I'm not sure I see that directory being used: the fixtures element on the classpath seems to be the only one that is not absolute. That might be causing problems. Try an absolute path for that dir

Answer 15 · 2018-01-31T22:20:20.000Z

I've tried an absolute path too and I get the same result. It's very strange!

I can try building a new distro based upon yours and adding DbFit, etc, into it instead to see if that helps.

(I've been playing with XmlHttpTest and nearly have something working but I'm doing something silly most likely but posted that on stackexchange).

Answer 16 · 2018-02-01T06:23:20.000Z

I'm sorry I can't provide an easy answer. There might be some conflict in versions of libraries used.

I have no personal experience with dbFit. I've done a few tests with jdbc slim (which I added as a maven dependency to my fitnesse installation) and that worked together quite well.

Answer 17 · 2018-02-01T08:45:10.000Z

The DbFit district uses a vanilla Fitnesse JAR from the central repo and my classpath excludes the DbFit JARs.

Could there be and other file dependencies that I’ve not copied over?

Answer 18 · 2018-02-01T09:27:53.000Z

I think I've cracked it. Somewhat embarrassingly I think I was mixing the binaries from your 3.15.1 release with the 4.0.0-SNAPSHOT release from the DbFit upcoming distro. They have slightly different FitNesse versions bundled.

By copying in the following directories:-

fixtures
plugins
target
webdrivers

I can run both my DbFit/Fitlibrary suites as well as test SOAP web services. Great!

Is this something that would be worth documenting as part of your project for other users wishing to add your binaries to their installations?

Answer 19 · 2018-02-01T15:04:03.000Z

Glad to hear you managed to get it to work. I'm pretty sure you don't need the target directory. And as long as you are not doing any browser testing, web drivers will not be needed either.
The maven-classpath plugin can be removed from the plugins folder (if you don't use !pom in the wiki).
Does it still work in that case?

If you are willing to do a short write-up about your experiences, we could add that to the wiki on GitHub. Is that something you're interested in?

Answer 20 · 2018-02-02T09:32:56.000Z

If you are willing to do a short write-up about your experiences, we could add that to the wiki on GitHub. Is that something you're interested in?

Yes. I can do that. I'll help to get the new DbFit release out first then write something up and get back to you.

Answer 21 · 2018-07-10T18:37:20.000Z

Hello, i have a fitnesse testing framework, but now i need to upgrade my browser, so i need to update all my libraries. Does someone knows the latest versions for firefox, selenide, selenium and Fitnesse so they can work properly together????

Answer 22 · 2018-07-10T20:33:08.000Z

Are you using this sample project, or some other fitnesse/selenium setup.

If you are NOT using the approach in this project I cannot advise you in general, as it depends on what (which versions) you are currently using and maybe even how you are using them. It might be a small matter of replacing some versions/jars and web driver executables. It might be more complex.

If you are using this sample project it is a matter of updating the version numbers for fitnesse and hsac-fitnesse-fixtures as described in the README

Answer 23 · 2018-07-10T20:34:16.000Z

@MMatten have you ever gotten 'round to that write-up we discussed?

Answer 24 · 2018-07-10T20:54:41.000Z

No, i'm not using this project as a base.
I have Selenium 2.47.1 firefox V32 selenide 2.17 and Fitnesse 20150424

Answer 25 · 2018-07-11T07:43:38.000Z

@fhoeben sorry, not yet. However I think my initial problems were down to FitNesse version conflicts. It seems all I needed to do was to take the JARs from DbFit and add them to your distro, or in fact the fixtures directory from your distro and add them to the master (current FitNesse version) build of the DbFit project.

I can write this up. Where do you think it should go? On your project Wiki or in the README?

Answer 26 · 2018-07-12T06:38:03.000Z

If it really was that simple a write-up might not be needed (we can point people to this issue).
But for a bit more elaborate description of which jars to put where, and what is needed in the wiki pages, a wiki page in this project seems like a good place.