-
Notifications
You must be signed in to change notification settings - Fork 571
Move starter proxy responsibilities into proxy set. #537
Conversation
Clean up formatting and remove unused imports.
Stop cleanup happening for idle outside of a test session
* Also make it possible to disable testing bot via a buildArg, this is to allow builds on sites where testing bot is blocked due to organisational Internet policies.
Restore testing bot
Request for Comment - Move starter proxy responsibilities into proxy set.
/retest |
Codecov Report
@@ Coverage Diff @@
## master #537 +/- ##
=============================================
- Coverage 79.83% 60.32% -19.52%
+ Complexity 582 472 -110
=============================================
Files 33 36 +3
Lines 2742 2999 +257
Branches 234 249 +15
=============================================
- Hits 2189 1809 -380
- Misses 409 1052 +643
+ Partials 144 138 -6 |
OK, so now Travis is passing! |
Teardown re-registered proxies so that their threads are stopped gc'd.
@dspasojevic I think the email account you used for the commits is not associated to your GitHub account, so the commits are not being associated to your GitHub user. |
Thanks for the heads up @diemol. I've linked my work accounts. It looks like the commits are correctly associated now. |
@diemol Anything left to test or change now? Very excited about getting this merged and to get a new release of zalenium 😸 |
@peerster the thing is that some unit tests are failing now, and even if the integration tests are passing, I'd like to review the unit tests first :) |
I just had a peek at why the test is failing, it's because the autostartproxy isn't expecting the proxy to register, so it doesn't accept the proxy registration |
Thanks for looking @pearj. I added a |
👍 |
🚀 |
Hi @diemol, with @pearj's help, I've fixed the failing unit tests. Sorry - I should have checked those before pushing up. The tests in Do you think that it would be good to write some additional integration tests (e.g. test killing containers in minikube, etc) rather than writing more unit tests that involve quite elaborate mocks? |
👍 |
1 similar comment
👍 |
Comes from #527