Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🧪 Testing: Fill in unit test coverage for initializeWithOptions.ts #873

Closed
3 tasks done
JoshuaKGoldberg opened this issue Sep 22, 2023 · 1 comment · Fixed by #1631
Closed
3 tasks done

🧪 Testing: Fill in unit test coverage for initializeWithOptions.ts #873

JoshuaKGoldberg opened this issue Sep 22, 2023 · 1 comment · Fixed by #1631
Labels
area: testing Improving how the repository's tests are run and/or code is tested status: accepting prs Please, send a pull request to resolve this!

Comments

@JoshuaKGoldberg
Copy link
Owner

Bug Report Checklist

  • I have tried restarting my IDE and the issue persists.
  • I have pulled the latest main branch of the repository.
  • I have searched for related issues and found none that matched my issue.

Overview

Splitting out of #869: the initializeWithOptions function is not currently unit tested. I'd love to see some unit tests added for it!

https://app.codecov.io/gh/JoshuaKGoldberg/create-typescript-app/blob/094b253411168038a2c7585e5172f8b773c18ea2/src%2Finitialize%2FinitializeWithOptions.ts

Additional Info

It'll be a little verbose to set up, but a unit test file should be able to Vitest mock out all the functions being called (writeStructure, writeReadme, etc.). And it'll likely have to mock out withSpinners, too, to directly call each of the functions provided in order.

@JoshuaKGoldberg JoshuaKGoldberg added status: accepting prs Please, send a pull request to resolve this! area: testing Improving how the repository's tests are run and/or code is tested labels Sep 22, 2023
@JoshuaKGoldberg JoshuaKGoldberg changed the title 🛠 Tooling: Fill in unit test coverage for initializeWithOptions.ts 🧪 Tooling: Fill in unit test coverage for initializeWithOptions.ts Sep 22, 2023
@JoshuaKGoldberg JoshuaKGoldberg changed the title 🧪 Tooling: Fill in unit test coverage for initializeWithOptions.ts 🧪 Testing: Fill in unit test coverage for initializeWithOptions.ts Sep 22, 2023
JoshuaKGoldberg added a commit that referenced this issue Aug 15, 2024
## PR Checklist

- [x] Addresses an existing open issue: fixes #873
- [x] That issue was marked as [`status: accepting
prs`](https://github.com/JoshuaKGoldberg/create-typescript-app/issues?q=is%3Aopen+is%3Aissue+label%3A%22status%3A+accepting+prs%22)
- [x] Steps in
[CONTRIBUTING.md](https://github.com/JoshuaKGoldberg/create-typescript-app/blob/main/.github/CONTRIBUTING.md)
were taken

## Overview

As the issue suggested, this was a fair bit of setup. But I feel better
now.

Also swaps out a `0` that was just coincidentally the same as the proper
`StatusCodes.Success`.

💖
Copy link

🎉 This is included in version v1.71.0 🎉

The release is available on:

Cheers! 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: testing Improving how the repository's tests are run and/or code is tested status: accepting prs Please, send a pull request to resolve this!
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant