You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd gladly create a travis-ci config for continuous delivery to nuget which would only require internal setup on the travis platform and be configured using environment variables.
e2e Testing
I would also like to add e2e unit-testing, would there be a possibility the project can have access to an unbilled e2e testing zone which we could use to ensure nothing in between broke?
Running this test before releasing it through the CI.would ensure no broken interfacing occurs in the released nuget package.
Only triggering it on tags would ensure there's no overuse or perhaps abuse of this zone.
Further feedback would be appreciated.
The text was updated successfully, but these errors were encountered:
As you may already know, I'm trying to get the project fully unit-tested to ensure functionality.
CI using Travis: #8
I'd gladly create a travis-ci config for continuous delivery to nuget which would only require internal setup on the travis platform and be configured using environment variables.
e2e Testing
I would also like to add e2e unit-testing, would there be a possibility the project can have access to an unbilled e2e testing zone which we could use to ensure nothing in between broke?
Running this test before releasing it through the CI.would ensure no broken interfacing occurs in the released nuget package.
Only triggering it on tags would ensure there's no overuse or perhaps abuse of this zone.
Further feedback would be appreciated.
The text was updated successfully, but these errors were encountered: