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

Run integration tests on a nightly basis #993

Closed
2 tasks done
Windos opened this issue Apr 14, 2023 · 1 comment · Fixed by #994
Closed
2 tasks done

Run integration tests on a nightly basis #993

Windos opened this issue Apr 14, 2023 · 1 comment · Fixed by #994
Assignees
Labels
5 - Released The issue has been resolved, and released to the public for consumption NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product
Milestone

Comments

@Windos
Copy link
Member

Windos commented Apr 14, 2023

Checklist

  • I have verified this is the correct repository for opening this issue.
  • I have verified no other issues exist related to my request.

Is Your Feature Request Related To A Problem? Please describe.

Integration tests take a long time to run, and they don't need to be run on every commit.

Describe The Solution. Why is it needed?

Current testing that happens on every commit should only run unit tests. Full test suites should instead be run on a schedule.

Additional Context

No response

Related Issues

@Windos Windos self-assigned this Apr 14, 2023
@Windos Windos added the 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint label Apr 14, 2023
Windos added a commit to Windos/ChocolateyGUI that referenced this issue Apr 17, 2023
Adds the TeamCity schedule trigger feature and adjusts the Call Cake
build step to adjust the testExecutionType based on how the build was
triggered.
Also removes the version statement which is not needed.
gep13 pushed a commit to Windos/ChocolateyGUI that referenced this issue Jun 9, 2023
Adds the TeamCity schedule trigger feature and adjusts the Call Cake
build step to adjust the testExecutionType based on how the build was
triggered.
Also removes the version statement which is not needed.
gep13 added a commit that referenced this issue Jun 9, 2023
(#993) (ENGTASKS-2347) Run integration tests only on scheduled builds
@gep13 gep13 closed this as completed in #994 Jun 9, 2023
@gep13 gep13 added NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product 4 - Done Code has been added to the repository, and has been reviewed by a team member and removed 0 - Backlog Issue is accepted, but is not ready to be worked on or not in current sprint labels Jun 9, 2023
@gep13 gep13 added this to the 2.1.0 milestone Jun 9, 2023
Windos added a commit to Windos/ChocolateyGUI that referenced this issue Jun 11, 2023
gep13 added a commit that referenced this issue Jun 12, 2023
(#993) (fix) Correct syntax in KTS file, duplicate scriptContent assignment
gep13 added a commit that referenced this issue Jun 29, 2023
* release/2.1.0:
  (maint) Update to latest version of chocolatey.lib
  (maint) Update GRM configuration file
  (maint) Remove version bump in nuspec file
  (build) Use latest Chocolatey.Cake.Recipe package
  (maint) Switch to Http for variable names
  (#1014) Add advanced option to ignore cached items
  (#1014) Ignore cached files on forced outdated check
  (build) Make build files consistent with others
  (#993) (fix) Correct syntax in KTS file
  (#993) Add TC schedule trigger
  (maint) Fix StyleCop warnings
  (#980) Use assembly location when debugging
  (maint) Update to released alpha package
  (#1003) Handle null keys during source translation
  (#1005) Normalize version numbers
  (maint) Add banned api analyzer
  (maint) Remove usage of obsolete methods
  (maint) Update to latest Chocolatey.Lib package
@gep13 gep13 added 5 - Released The issue has been resolved, and released to the public for consumption and removed 4 - Done Code has been added to the repository, and has been reviewed by a team member labels Jun 29, 2023
@choco-bot
Copy link

🎉 This issue has been resolved in version 2.1.0 🎉

The release is available on:

Your GitReleaseManager bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5 - Released The issue has been resolved, and released to the public for consumption NO RELEASE NOTES Should not be included in the release notes - not enhancing or fixing end product
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants