Releases: dbfit/dbfit
Releases · dbfit/dbfit
DbFit 2.0.0-RC2
Release date: 26th Feb 2013
- DbFit upgraded to FitNesse release v20130216:
- WISYWIG editor: multiline cell editing bugfixes.
- DbFit now bundled with FitSharp 2.2 (.NET 4.0). This:
- allows combining DbFit and .NET fixtures in the same test
- expands database supports in .NET mode to MS Sql Server, Oracle, MySQL and Sybase
- Support for the Oracle NCLOB datatype (issue #14).
- The DbFit Acceptance Test pages have been moved to a subwiki (issue #15).
DbFit 2.0.0-RC1
Release date: 16th Jan 2013
- Even more databases supported. The full list:
- Oracle
- Microsoft SQL Server
- DB2
- Derby
- HSQLDB
- MySQL
- PostgreSQL
- DbFit upgraded to FitNesse release v20121220 which includes:
- a refresh of the user interface
- a snazzy WISYWIG editor (which makes page editing a lot easier)
- a slew of FitNesse fixes
- New home on GitHub for the project sources and documentation
Dbfit 1.1
This is a placeholder for the DbFit 1.1 release (originally released on SourceForge).
DbFit 2.0.0-RC5
Release date: 25th May 2013
New features
- Database password encryption (#97, #104)
- Oracle: support for Oracle BOOLEAN types (#80, #87)
Minor improvements and bugfixes
- Oracle: Unclear stacktrace when the JDBC connector is missing (#27, #75)
- Postgres: support the "unknown" datatype (#92)
- DB2: support the "DECFLOAT" datatype (#114)
- better error message for unsupported Oracle data types (#115)
Documentation improvements
- documentation of database connection tables: Connect and Connect using file (#94)
- add link to the DbFit history article (#102)
Development and project improvements
DbFit 2.0.0-RC4
Release date: 28th Mar 2013
Features
Documentation improvements
- Reinstated What's wrong with xUnit
- Added the DbFit test catalog
Bugfixes
- Exception for stored procedure input parameters of type NUMBER in standalone mode (#58)
- Synonyms followed properly when using Oracle (#52, #50)
- Derby: inconsistent handling of case across different fixtures (#22)
- Inconsistent syntax for calling stored proc without parameters (#21)
For the full list of solved issues, see the milestone on GitHub.