minhphien / migratordotnet

Automatically exported from code.google.com/p/migratordotnet
0 stars 0 forks source link

Request: Documentation for running tests #158

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
Could someone please add a section to the "Contributing" page that explains how 
to run the tests?

What are the tests.exclude and tests.app.config properties for in 
local.properties.  tests.exclude appears to be for excluding tests for certain 
types of databases, but what should the value be?  I want to start out by just 
getting tests running in SQLite so I modified the value to be 
"Oracle,SqlServer,PostgreSQL,Mysql" based on the names of the 
Migrator.Providers, but the tests are trying to connect to a SQL Server and a 
Postgresql DB.

I'd love to be able to contribute ... I'll post back if I manage to figure this 
out.

Thanks!

Original issue reported on code.google.com by remitay...@gmail.com on 19 Sep 2010 at 7:55

GoogleCodeExporter commented 9 years ago
Regarding tests.exclude, this is used to exclude NUnit tests with a certain 
category.  Reference: 
http://nant.sourceforge.net/release/latest/help/types/categories.html

The categories used by Migrator.NET at the current time are:
MySql
Oracle
Postgre
SQLite
SqlServer
SqlServer2005
SqlServerCe

Original comment by remitay...@gmail.com on 19 Sep 2010 at 8:01

GoogleCodeExporter commented 9 years ago
To run all tests: nant -buildfile:default.build test

To exclude ALL tests that run against an actual database, use this property in 
your local.properties:
<property name="tests.exclude" 
value="MySql,Oracle,Postgre,SQLite,SqlServer,SqlServer2005,SqlServerCe"/>

For example, if you only want to run SQLite tests, use this property:
<property name="tests.exclude" 
value="MySql,Oracle,Postgre,SqlServer,SqlServer2005,SqlServerCe"/>

Original comment by remitay...@gmail.com on 19 Sep 2010 at 8:04

GoogleCodeExporter commented 9 years ago
I can't edit the Wiki pages, so I added that ^ as a comment on the Contributing 
page.

You can probably close this issue now, as I added a comment to the page.  Looks 
like it took me longer than I thought to figure this out, just had to grep thru 
the code a bit.

Thanks!

Original comment by remitay...@gmail.com on 19 Sep 2010 at 8:05