bssw-psip / bssw-psip/example-ptc-issues

Test Coverage

Open
#7 0 comments 0 reactions 0 assignees View on GitHub
PTC
Dominant language
No language data
Stars
2
Forks
2
PR merge metrics
No merged PRs in 30d

Description

Current Score (0-5): 3

| Score | Description |
| :-------------: | :------------- |
| 0 | Little or no independent testing. Functional testing via users. |
| 1 | Independent functional testing of primary capabilities. |
| 2 | Primary functional testing, some unit test coverage. #10 |
| 3 | Comprehensive unit testing, primary functional testing. |
| 4 | Comprehensive unit testing, functional testing for documented use cases. #9 |
| 5 | Comprehensive unit, use case functional testing; test coverage commitment. |

## Comments

1. **Functional testing**: Testing capabilities from user's perspective. Many functions can be called. Good for usability assurance. Insufficient to protect against some regressions. Difficult to isolate regressions. Can require extensive test execution times.
2. **Unit testing**: Isolated, independent testing of functions and methods. Enable test-driven development, rapid test execution, fault isolation. Insufficient to ensure functional correctness.
3. **Comprehensive**: Does not mean 100% line coverage, but sufficient coverage to detect most errors. Experts suggest various metrics such as 80% or more line coverage, or some similar high percentage of function point coverage.
4. **Commitment**: Team is committed to writing comprehensive tests concurrent with functionality.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.