The code that is developed is covered by Unit tests and Component tests. Some of the component tests are functional tests and can be found in '.spec.ts' files As a tester you should be able to understand what is being tested by the title and the simple implementation of the test. Understanding these tests will give you more trust on what to test when exploratory testing in the feature branch. It also determines what needs to be automated in the other test types.

Tests written by DEV and reviewed by DEV and QA

Right before the code is going to be merged to feature branch there is a Pull request where you can easily read what is newly added with the task. This is where you as QA will look for the .spec files. If reading .spec files is too complicated, DEV can also be requested to deliver a list of tests created with a logical name, in this way the QA can advice on scope and completeness of the tests.

The Pull request should be connected to the US on the board. *If it is not please ask the developer to do so.

Follow this link and you will then be able to see the files that have been added or changed for the functionality. This is where you look for the .spec files as shown below:

**Checklist for functional test cases; Is the title clear and does it scope to the functionality it is testing?

• All edge cases (if possible) are tested
• Tests results are visible in build documentation

Comments You can add comments and questions to the Pull request if you think that there is anything that could be done better in the tests. Keep in mind that these tests can be a bit technical. It is good practice to keep a short line with the developer and have him explain you so you can get the trust and T&R check that you need for the code added.