Lighthouse has a new layout. Prefer the old one? Return to the old layout, and switch back any time from the link at the top of each page.

Error - "Infinitest disabled. Errors in workspace"

#38

Hi there,

I just bought the inifitest developer package and after installing in eclipse 3.4.2 here on mac osx 10.5 the infinitest bar has a green star icon but the following message.

Infinitest disabled. Errors in workspace

I already made sure that under preferences... ->infinitest the checkbox for continuously testing is checked. The project that I want to run the test for has no errors, other projects in workspace not related to that project have errors, but that can't be the reason why the tests are not run for that project, or? how can i set to run tests for a specific project i'm working on?

Thanks.

Dominik

Reported by Dominik · February 23rd, 2010 @ 08:14 PM

State: new
Milestone: none
Assigned to: benrady (at gmail) benrady (at gmail)

Activity

  1. benrady (at gmail)
    benrady (at gmail)

    Infinitest will not run tests if any of your classes are in an invalid state
    (if you have compile errors) or if there are any other errors in the workspace.

    February 24th, 2010 @ 03:15 AM

  2. Dominik
    Dominik

    Thanks for the fast reply,

    is there any way of setting infinitest to just check some projects and not all the workspace? Right now this would mean that I would need to close all projects that somehow have an error in it in order to make inifinitest work for my current project...

    Dominik

    February 24th, 2010 @ 03:46 AM

  3. benrady (at gmail)
    benrady (at gmail)

    Not currently.

    Out of curiosity, why are you including projects in your workspace that have
    errors? Can't you fix them?

    February 24th, 2010 @ 03:54 AM

  4. Dominik
    Dominik

    I can see several scenarios where some of my projects might be in an error prone state. For example I'm using a imported project to which I haven't figured out all lib dependencies, but the subset of classes of that project that I'm using is compiling just great and working in another project of mine.
    Or I might be doing some trial code at one time in a personal project that might also lead to some errors, but I don't want that to hinder my test classes in a professional project from running.
    So I was really surprised to see that all the projects in a workspace need to be clean in order to be able to run test classes in a project I'm currently working on. I've been using the inifitest.jar before that and I was very pleased with how it worked. (this didn't have any dependency on all projects in the workspace but just the project I launched it for) So expecting the same behaviour and seeing that after actually paying for it it is working not as smoothly is a bit disappointing.
    Thanks for your quick reply.

    February 24th, 2010 @ 03:36 PM

  5. benrady (at gmail)
    benrady (at gmail)

    Agreed that disabling the tests should be limited to a specific project.

    May 18th, 2010 @ 01:54 PM

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.