Make a tested instance

Registered by Federico Razzoli on 2013-02-16

For now, a single STK/Unit instance tries to test itself using 2 TCs (1 for assertions, the other for the core library). This is not bad for assertions, which can be completely tested. But of course only some procedures from the core lib can be tested this way.

This blueprint aims to make a separate instance of STK/Unit which will be tested by the main instance.

This will be possible when Macros will be implemented (in another STK project). In the main .sql file, the database name will be a Macro, so that it will be possible to transform it in the main instance or in the tested instance, simply by specifying 2 different values as DB name. Other files will contain references both to the main instance and to the tested instance (because they will use one instance to test the other one).

This feature is needed to test some planned features.

Blueprint information

Status:
Started
Approver:
Giacomo Picchiarelli
Priority:
Essential
Drafter:
Federico Razzoli
Direction:
Approved
Assignee:
Federico Razzoli
Definition:
Discussion
Series goal:
Accepted for trunk
Implementation:
Needs Infrastructure
Milestone target:
milestone icon 2.0.0
Started by
Federico Razzoli on 2013-02-19

Related branches

Sprints

Whiteboard

(?)

Work Items

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.