googleapis / googleapis/google-cloud-swift
cleanup StorageW1R3 structure
- Dominant language
- Swift
- Stars
- 26
- Forks
- 10
- Avg merge
- 12h 57m
- Merged PRs (30d)
- 213
Description
The code for this test should live in a sub-directory of `Sources/`, and be implemented as a library. That way we can write unit tests for some of the components.
The main program should be a small executable target with just a main function that calls the main class.
The integration test should just be a regular `@Suite` that configures and invokes the main class.
Contributor guide
Research direction
Locate the StorageW1R3 test code and the current package structure under Sources/, then inspect how the main program and integration test are wired. Done means the implementation is a library, the executable target contains only a main function calling the main class, and the integration test is a regular @Suite that configures and invokes that class.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- swift
- Domain
- build-system, testing
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 64/100