33 lines
1.7 KiB
Markdown
33 lines
1.7 KiB
Markdown
## Test strategy
|
|
|
|
The test strategy for this repository involves using Go testing frameworks to ensure the correctness of the task step display name functionality in the `models/actions/task_test.go` file. The tests will cover various scenarios, including valid and invalid input, to ensure that the function behaves as expected.
|
|
|
|
## Test tactics
|
|
|
|
The following test tactics will be used:
|
|
- Unit testing: Testing individual functions or methods within the task step display name functionality.
|
|
- Integration testing: Testing the interaction between different components of the task step display name functionality.
|
|
|
|
## Test cases (mapped to use cases)
|
|
|
|
1. **Use case: Test Task Step Display Name**
|
|
- **name:** `Test MakeTaskStepDisplayName`
|
|
- **trigger:** Running tests for `models/actions/task_test.go`
|
|
- **components:**
|
|
- **models/actions/task_test.go** (file) - Go code for testing tasks
|
|
- **uses:** `github.com/stretchr/testify/assert`
|
|
- **outcome:** All tests pass
|
|
- **evidence path:** [code/gitjet/core-scm/branch/main/tag/no-tag/commit/28d1ee1dd5e3b8ae4b351fee8d82e47bb5e8110f/file/models/actions/task_test.go#chunk0](https://gitjet.ru/gitjet/core-scm/branch/main/tag/no-tag/commit/28d1ee1dd5e3b8ae4b351fee8d82e47bb5e8110f/file/models/actions/task_test.go#chunk0)
|
|
|
|
## Smoke
|
|
No smoke checks exist for this repository.
|
|
|
|
## Regression
|
|
Regression testing will be performed after each code change to ensure that the task step display name functionality continues to work as expected.
|
|
|
|
## Edge cases
|
|
|
|
Edge cases to consider during testing include:
|
|
- Testing with empty input strings
|
|
- Testing with special characters in the input strings
|
|
- Testing with large input strings |