I've been reverting my project repeatedly back to a clean version with no unit testing target, classes or schema configurations (in the project file?)

But even after I cleaned out that "cache" location that you mention AppCode still thinks I have a Testing Group in the Project, with "missing" files in red. These are not in the project.pbxproj file. Here's what it looks like:

If I clone the project out from its git hub repository (listed in my original post) into a new directory it's fine and reads it fresh and apparently OK.

So the question is: apart from the cache location that you listed, and the project.pbxproj file what other locations/files does AppCode (and/or Xcode) use to "configure" the project? For example a freshly cloned repository from github lacks the files "project.xcworkspace" and "xcuserdata" that are in the project bundle dir once the project has been opened into the IDE (into Xcode? Appcode? either? - loading a clean project into AppCode seems to create the "xcuserdata" file, certainly). Clearly git's not comitting these files (I created the repo on github as an Xcode project and those files are in .gitignore).  I guess they may contain something that alters either AppCode or Xcode's behaviour which is the cause of my issues (i.e. old, apparently "sticky" and stale project configuration).

I also see a ".idea" directory (empty) likewise in a clean, but once loaded into AppCode, checkout.

I hate magic files for this reason. Appcode ought to have a "clean out this project of non-source controlled configuration" option which empties the cache and trashes these files or something. I think what's been happening is that I've been "reverting" the one project dir when my attempt to fix my problems has failed ... but because these files are left there it "inherits" the left over bad configuration which is reactived when I try to apply the fix. Thus is looks like what is supposed to work, won't. And when I saw the above .. it clicked that //there must be magic IDE files in the project//  ... I am just trying some stuff on a clean check out and I got past my *first* point of failure (although I haven't restored all my tests just yet so not out of the woods quite at this point!).

Is there a guide to these magic files and what they do? So that we know which file to delete under what circumstance?

thanks

scot

OK I've been able to narrow it down to what starts the grief although I've not been able to get rid of it.

Bear in mind these are tests I originally developed in AppCode in order to build my basic data components so they once passed (until I tried renaming the test class and found myself in a world of hurt).

I created a brand new Test Target in Xcode according to the relevant Apple page that's here: - http://developer.apple.com/library/mac/#documentation/developertools/Conceptual/UnitTesting/02-Setting_Up_Unit_Tests_in_a_Project/setting_up.html

I get a "test.h" interface and a "test.m" impl which when run in Appcode or Xcode runs but fails (because STFail("tests not implemented")). Removing the STFail line causes tests to pass (hey this TDD thing is easy, I have a green bar already!! ;-) )

I then add a couple of things to my test.h to  start to make it have the the interface I need, here it is in toto:

//
//  LatinOnlineWordLookupTests.h
//  LatinOnlineWordLookupTests
//
//  Created by Scot Mcphee on 15/03/13.
//  Copyright (c) 2013 Scot Mcphee. All rights reserved.
//

#import <SenTestingKit/SenTestingKit.h>
#import "OWLMorphData.h"
#import "OWLMorphDataObserver.h"

@interface LatinOnlineWordLookupTests : SenTestCase <OWLMorphDataObserver>

@property OWLMorphData *morphData;

@end

Then I add some things to my implementation so it looks like this:

//
//  LatinOnlineWordLookupTests.m
//  LatinOnlineWordLookupTests
//
//  Created by Scot Mcphee on 15/03/13.
//  Copyright (c) 2013 Scot Mcphee. All rights reserved.
//

#import "LatinOnlineWordLookupTests.h"

@implementation LatinOnlineWordLookupTests
    BOOL wasRefreshed = NO;
    BOOL wasError = NO;
    @synthesize morphData;

    - (void)setUp {
        [super setUp];
        //[self setMorphData: [[OWLMorphData alloc] init]];
    }

    - (void)tearDown {
        [super tearDown];
    }

    - (void)testNothing {
        STAssertEquals(0, 0, @"0 must equal 0");
    }

#pragma LatinMorphDataObserver protocol methods
    - (void)refreshViewData:(OWLMorphData *)latinMorph {
        wasRefreshed = YES;
    }
    - (void)showError:(NSError *)error forConnection:(NSURLConnection *)connection {
        wasError = YES;
    }
    - (void)showError:(NSException *)exception1 forSearchTerm:(NSString *)searchTerm {
        wasError = YES;
    }

@end

this runs and passes (hey, 0==0, who would have thought?) ...

But see that one line in in setUp() ... where I initialise the class I want to test? If I uncomment it, I get ...

(BTW: tip -- it would be nice to be able to copy more than one of those lines at a time from the "Messages" window)

Of course, in the app itself I can initialise the class just fine and it actually works, because I wrote the class initially with TDD. I'm just trying to now restore the ability to run new tests ...

This was all done from a "clean & fresh" checkout of my project to bypass the "magic files" not in the repo.

XCode ... same behaviour ... so I realise it's probably a project files setup issue ...