You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficcontrol.apache.org by GitBox <gi...@apache.org> on 2020/02/18 18:40:11 UTC
[GitHub] [trafficcontrol] rob05c commented on issue #4374: Create API v2
tests
rob05c commented on issue #4374: Create API v2 tests
URL: https://github.com/apache/trafficcontrol/pull/4374#issuecomment-587634511
>I think it should have the option to run v1 tests as a regression check and in my opinion by default run both. There is going to be (already is) a lot shared code between v1 and v2 and we need to make sure we are not causing any regressions since we as a community are supporting v1.
+1 Though, abstracting the tests to support multiple versions sounds like a lot of overhead, especially for the 1.x endpoints that shouldn't be changing much.
What if we delete the 1.x tests from the repo, and the operating procedure is for build systems to check out the 4.0.x branch (the latest release before 2.x was added), and run those tests against master TO? And if there are new 1.x tests (which should be rare), we add them to the 4.0.x branch. Seems like that would be easier to manage and maintain.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services