search

google-code-export / dataobjectsdotnet

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

Remove all hardcoded connection URLs / connection strings from tests #584

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Currently we have lots of them.
This makes developing DO impossible without plenties of tricky configured
servers. Every connection information for tests should be overridable with
ease.

Possible API (in Core.Testing since we need this for Sql solution too):

enum ServerReference {
  SqlServer, // default sql server (for do tests)
  SqlServerNorthwind, // northwind in default sql server
  SqlServerAdventureWorks, // adventure works for default sql server

  SqlServer2005, // sql server 2005 (for do tests)
  SqlServer2005Northwind, // northwind in sql server 2005
  SqlServer2005AdventureWorks, // adventure works in sql server 2005

  SqlServer2008, // sql server 2008 (for do tests)
  SqlServer2008Northwind, // northwind in sql server 2008
  SqlServer2008AdventureWorks, // adventure works in sql server 2008

  PostgreSql, // default postgresql server (for do tests)
  PostgreSql82, // postgresql v8.2 (for do tests)
  PostgreSql83, // postgresql v8.3 (for do tests)
  PostgreSql84, // postgresql v8.4 (for do tests)

  Oracle, // default oracle server (for do tests)
  Oracle09, // oracle 9i2 (for do tests)
  Oracle10, // oracle 10g (for do tests)
  Oracle11, // oracle 11g (for do tests)
}

class ServerResolver {
  string GetConnectionString(ServerReference reference);
  UrlInfo GetConnectionUrl(ServerReference reference);
}

Original issue reported on code.google.com by denis.kr...@gmail.com on 18 Jan 2010 at 11:40

GoogleCodeExporter commented 9 years ago

Original comment by denis.kr...@gmail.com on 2 Feb 2010 at 8:48