# Testing the new foundation

In order to verify that the new foundation is working, there are several things we should test.

## CI Testing

### Test candidate 1: A docker container with no dependency to npm packages

Candidate: `/Users/andiolsi/work/seaspots/services/seaspots-homepage`

### Test candidate 2: A npm package built with npm

Candidate: `/Users/andiolsi/work/olsitec-nci/lib/olsicrypto`

### Test candidate 3: A npm package built with bun

Candidate: `/Users/andiolsi/work/olsitec-nci/lib/document-engine`

### Test candidate 4: A non-artifact versioned repo

Candidate: `/Users/andiolsi/work/olsitrack2/api`

### Test candidate 5: A docker container with dependency to npm packages

Candidate: `/Users/andiolsi/work/olsitrack2/services/token-service`

Has an (albeit oudated) dependency on olsicrypto (candidate 2).

## semantic-release testing

Create some test git repo, push it to master/main. Expected outcome: 1.0.0

Pull rebase, commit a feat commit. Expected outcome 1.1.0

Pull rebase, commit a fix/chore commit. Expected outcome 1.1.1

Pull rebase, commit a commit with an `!`, such as `feat!`. Expected outcome 2.0.0

Pull rebase, commit a commit with `BRREAKING CHANGE` or `BRREAKING CHANGES`. Expected outcome 3.0.0

## linter testing

Push something with a eslint error in it. Expected outcome: Job exit non-zero

Push something with a yamllint error in it. Expected outcome: Job exit non-zero