This repository has been archived by the owner on Feb 1, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 53
Add E2E tests #54
Comments
Issue-Label Bot is automatically applying the labels:
Please mark this comment with 👍 or 👎 to give our bot feedback! |
part of #44 |
/assign |
During the E2E test, do we need to display the client's waiting time or progress for the job ? If we do, I think we probably need to write a clientset file. |
At the beginning, we can leave this to a todo list if it is only used to
observation.
…On Sat, May 9, 2020 at 1:56 PM xfate123 ***@***.***> wrote:
During the E2E test, do we need to display the client's waiting time or
progress for the job ? If we do, I think we probably need to write a
clientset file.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#54 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAK5R6MYXGXXFX7ZAJ34ZNTRQW7ONANCNFSM4M4U7FOA>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
. E2E tests should be run on presubmit, postsubmit, and periodically
. Tests should cover deployment (kustomize packages) as well as the application functionality
The text was updated successfully, but these errors were encountered: