>> >> 1) if the online build is going to run tests, does it automatically load >> from the SVN http://svn.geotools.org/geotools/trunk/gt/build/fixtures/ >> path into the testing environments home directory? >> > Not as written, its up to the developer to copy them into their home > directory, and up to the person admining the build server to manage this. > OK - will write this into docs to make it clear. Why do fixtures live here rather than in the modules themselves? (presumably for re-use, in which case the provider of on online resource should probably put some comments about usage policy, resource such as table naming etc. >> 2) the "nogeos" fixture looks fine for me - do I re-use it or clone it >> to create an online test for geometryless? >> > sure. > as in either option is fine? >> 3) is there a resource naming convention to avoid resource clashes? >> > we came up with the convention of prefixing the fixture with the name of > the module. So if you want to load the geos fixture for postgis, your > fixture id is "postgis.nogeos". > OK - I think I understand - the _filename_ is nogeos.properties. Not sure what the fixture ID is used for >> 4) if other people are running online tests against the same fixture, >> how do we avoid resource contention/corruption? >> - if the resource is left available, and its readonly, then we want >> mvn clean or something to remove it, otherwise the test can create it if >> its missing perhaps? >> > This is a tough one. One thing we thought of for postgis was to run all > the tests in a transaction. > that would work only for JDBC based systems. I'll try to write my tests to assume that if the table is there, its OK, and use test failures to highlight any issues requiring destruction and rebuilding of the test data set.
>> 5) without any fixtures in my home directory, when I run mvn test -P >> online it tries to connect - but seems to hit the local database and >> fail - this seems inconsistent with the write-up "it will skip tests if >> it cant find a fixture" - or does it mean that online tests are run _in >> addition_ to the default set - which makes little sense IMHO. >> >> > You are probably hitting tests that haven't been converted over yet > would be my guess. And yes, for a while things will be inconsistent. For > instance none of the wms online tests will adhere to this scheme yet. > This is only within the postgis module. not sure what "converted over" really means - as in the fixture loading strategy needs to be converted for each test suite? Rob A ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
