"2. Did this change brake existing functionality?"I'm not sure this is quite write...
hi Mike!, did u mean RIGHT?. Cheers, Reine.
"So we have taken advantage of this time by running tests via the presubmit system that finds all of the tests that are relevant to the change, runs the tests, and reports the results."I'm very curious to know how you guys figure out the range of relevant components. Is it analyzed from the ready-to-check-in code, or something else? The range could be extremely large or difficult to be marked, I think. Could you please shed some light on it?Thanks in advance.
Is there anyway I can convince the people I work with to use Unit testing? I mean they don't even use version control...How can I convince them that this is actually a good idea?
Andrew Leer: You don't need to convince all people at work, you just need to convince your boss. I would start easy with the source control thing, though.
I agree with Ryan. It would be very interesting to learn how you find "all of the tests that are relevant to the change".I would imagine you use the tests code coverage data to do so. Please enlighten us!
@Ryan @cuquii don't know how they do it.it could be reverse code coverage database for existing code
The comments you read and contribute here belong only to the person who posted them. We reserve the right to remove off-topic comments.