rob05c commented on issue #3056: Add experimental end-to-end test framework
URL: https://github.com/apache/trafficcontrol/pull/3056#issuecomment-442883207
 
 
   >a Traffic Control E2E test would talk primarily to Traffic Ops
   Well, it needs to to get the data, to make requests. But after that, its 
primary job should be making requests thru the Router/Edge. If we felt strongly 
about a non-Go test, I think it'd be ok to write a thin client in that language 
to just auth and the endpoints we need.
   
   >I've got some more thoughts on what types of functionality an E2E framework 
should have based on some experiences with our own in house regression tests. 
I'll try to write those up a bit later.
   
   +1 We can use all the input we can get for this kind of thing. No one person 
is going to think of all the cases we should test.
   
   >based on some experiences with our own in house regression tests.
   
   This is a total tangent, but while you're here, I have some other ideas 
about a "Data Validation" tool I think we should write. TC has a _ton_ of data 
constraints that the CDN simply doesn't function without. I've said since the 
beginning, I think those data constraints should be encoded in the DB; but 
there's some pretty strong resistance to that. So, I had an idea about the next 
best thing: a tool to validate them. (This is obviously similar to Voluspa). 
For example, Cache profiles MUST have a `health.polling.url` parameter. There 
are _countless_ data requirements like that. I think a tool to just get data 
from TO and verify requirements like that would be really easy to write, and be 
a big safety/confidence gain. It could be run all the time - every build, test 
upgrade, people could run it every 5 minutes in production even. 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to