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

SUI blueprint. CDK stack tests are missing #107

Open
frbrkoala opened this issue Aug 2, 2024 · 8 comments · Fixed by #164
Open

SUI blueprint. CDK stack tests are missing #107

frbrkoala opened this issue Aug 2, 2024 · 8 comments · Fixed by #164

Comments

@frbrkoala
Copy link
Contributor

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment

What is the outcome that you are trying to reach?

SUI blueprint CDK should have unit tests to validate new changes for possible regressions.

Describe the solution you would like

See other blueprints for examples

Describe alternatives you have considered

Additional context

Copy link
Contributor

github-actions bot commented Sep 2, 2024

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Sep 2, 2024
Copy link
Contributor

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Sep 13, 2024
@frbrkoala frbrkoala reopened this Sep 13, 2024
@github-actions github-actions bot removed the stale label Sep 14, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Oct 14, 2024
Copy link
Contributor

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 25, 2024
@frbrkoala frbrkoala reopened this Oct 28, 2024
@github-actions github-actions bot removed the stale label Oct 29, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Nov 28, 2024
Copy link
Contributor

github-actions bot commented Dec 8, 2024

Issue closed due to inactivity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Dec 8, 2024
@frbrkoala frbrkoala reopened this Dec 19, 2024
@github-actions github-actions bot removed the stale label Dec 20, 2024
Copy link
Contributor

This issue has been automatically marked as stale because it has been open 30 days
with no activity. Remove stale label or comment or this issue will be closed in 10 days

@github-actions github-actions bot added the stale label Jan 19, 2025
@frbrkoala frbrkoala linked a pull request Jan 24, 2025 that will close this issue
9 tasks
@frbrkoala
Copy link
Contributor Author

Fixed

@frbrkoala frbrkoala reopened this Mar 17, 2025
@github-actions github-actions bot removed the stale label Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant