-
Notifications
You must be signed in to change notification settings - Fork 12.1k
Adding Tomita as a CI/CD supervisor #874
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
Comments
Raising this to critical |
I approve of this message. |
Hello, we plan on working on adding your cat to our codebase after we finish working on increasing Elon Musk's tweet engagement. Thank you for putting this issue into our attention, we appreciate it. Have a great day! |
any progress ? also !! PLEASE DO NOT THE CAT !! libthecat has been deprecated since v6.94.20, use libkat ( KDE's fork for libthecat ) ( v1.33.7 ) instead |
THIS IS IMPORTANT |
libkat has been deprecated in favor of katqt |
Is your feature request related to a problem? Please describe.
Our integration tests have been lacking in terms of real-world simulation. We need a better way to test our code against bugs and errors that may arise in a live environment. Tomita, our orange stray cat, has shown to be an excellent bug catcher and can provide a more realistic test environment.
Describe the solution you'd like
We would like to add Tomita to our CI/CD pipeline for integration testing. This would involve setting up a dedicated testing environment for Tomita to run around in and catch bugs. We would also need to establish a way to monitor Tomita's activity and make sure he doesn't interfere with the codebase.
Describe alternatives you've considered
One alternative we've considered is using a virtual testing environment instead of a physical one with Tomita. However, this would not provide the same level of real-world simulation that Tomita could offer.
Additional context
We have attached a picture of Tomita for your reference. He is a very good cat and we believe he will make an excellent addition to our testing process.
The text was updated successfully, but these errors were encountered: