Tackler Test Tracking Database (T3DB)

This is Tackler's test tracking "database" (T3DB) for feature and test tracking.

Main purpose of T3DB is to ensure all features and error paths of those features are tested and validated, with minimal amount of overlapping and duplicate test cases.

T3DB also provides reverse mapping from test cases back to features, which are validated by that particular test case.

Performance testing

Tackler performance test setup and actual results described in Tackler performance test setup document.

T3DB files

T3DB consist of following files:

Main T3DB

• Main features

T3DB for TEP-1001

• Commodities

• Currencies

T3DB for TEP-1002

• Git Backend

T3DB for TEP-1004

• JSON output

T3DB for TEP-1005

• transaction filters

T3DB for TEP-1006

• Configuration settings for min, max scale

T3DB for TEP-1007

• Transaction set checksum

• Account selector checksum

T3DB for TEP-1008

• Account names

• Numerical Account names

T3DB for TEP-1009

• Txn Header Syntax (v2)

T3DB for TEP-1010

• Txn Geo Location

• Geo Location Filter

T3DB for TEP-1011

• Transaction Tags

T3DB for TEP-1012

• Custom timestamps for reports

T3DB for TEP-1013

• Configuration key change of Accounts CoA

T3DB for TEP-1014

• Equity Features and Enhancements

T3DB for TEP-1015

• Commodity Price Data Support

T3DB for TEP-1016

• Flat Balance and Balance Group Reports

Template for T3DB entry

T3DB format

T3DB uses YAML format for describing features, test cases and links between those.

T3DB schema is defined in following file:

• Schema for T3DB (YAML is the worst schema language in the world)

---

Tackler-T3DB is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.