Skip to content

Latest commit

 

History

History

test

Folders and files

NameName
Last commit message
Last commit date

parent directory

..

README.md

README.md

 
 

build_all.sh

build_all.sh

 
 

build_fpc.sh

build_fpc.sh

 
 

compil7.bat

compil7.bat

 
 

compilD2007.bat

compilD2007.bat

 
 

compilD2010.bat

compilD2010.bat

 
 

compilXE4.bat

compilXE4.bat

 
 

compilXE7.bat

compilXE7.bat

 
 

compilpil.bat

compilpil.bat

 
 

mormot2tests.dpr

mormot2tests.dpr

 
 

mormot2tests.lpi

mormot2tests.lpi

 
 

test.core.base.pas

test.core.base.pas

 
 

test.core.collections.pas

test.core.collections.pas

 
 

test.core.crypt.pas

test.core.crypt.pas

 
 

test.core.data.pas

test.core.data.pas

 
 

test.core.ecc.pas

test.core.ecc.pas

 
 

test.core.script.pas

test.core.script.pas

 
 

test.net.proto.pas

test.net.proto.pas

 
 

test.orm.core.pas

test.orm.core.pas

 
 

test.orm.extdb.pas

test.orm.extdb.pas

 
 

test.orm.network.pas

test.orm.network.pas

 
 

test.orm.sqlite3.pas

test.orm.sqlite3.pas

 
 

test.orm.threads.pas

test.orm.threads.pas

 
 

test.soa.core.pas

test.soa.core.pas

 
 

test.soa.network.pas

test.soa.network.pas

 
 

README.md

mORMot Test Files

Folder Content

This folder holds the regression tests defined for the mORMot Open Source framework, version 2.

MPL 1.1/GPL 2.0/LGPL 2.1 three-license

The framework source code is licensed under a disjunctive three-license giving the user the choice of one of the three following sets of free software/open source licensing terms:

  • Mozilla Public License, version 1.1 or later (MPL);
  • GNU General Public License, version 2.0 or later (GPL);
  • GNU Lesser General Public License, version 2.1 or later (LGPL), with linking exception of the FPC modified LGPL. This allows the use of our code in as wide a variety of software projects as possible, while still maintaining copy-left on code we wrote.

See the full licensing terms in the root folder of this repository for more information.

Testing Policy

Framework code is tested against code correctness via unit tests, to avoid behavior or performance regressions, and ease refactoring. We try to have the best code coverage possible, and avoid any unexpected problem when upgrading the firmware.