Error - "Infinitest disabled. Errors in workspace"
-
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. -
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
-
benrady (at gmail)
Not currently.
Out of curiosity, why are you including projects in your workspace that have
errors? Can't you fix them? -
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. -
benrady (at gmail)
Agreed that disabling the tests should be limited to a specific project.
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.