Why do cars need to have the right breaking system -Shalabh Varma & Manisha Awasthi

Editor's Notes

• #2: Manisha
• #3: ManishaThe question was asked to Jon Jagger (get some bio) by KevlinHenney (get some bio). A very common answer to the question is 'to stop'. But that was not what Kevlin has in mind. His answer was 'So you can drive faster'.His answer feels paradoxical which usually means there's a deep truth. Brakes allow you to stop when you want. Brakes allow you to stop where you want. They help you drive faster. Thinking about brakes allowing you to stop is thinking statically. Thinking about braking allowing you to drive faster is thinking dynamically.
• #4: ShalabhThink of a highway as an application that has been built. And you are driving a car on top of it, which could be thought of user flows - you use a flow to reach from one destination to the other. There would be multiple cars running on the highway to get to a certain destinations. What are the various ways in which you could go from say Pune to Nashik - you can walk, cycle, or use a motored way. If you would like to reach your destination sooner then you would look to go faster and the fastest way to go would be the motored way. Let us pick up a car.Think of yourself as sitting in the car driving. What could be the scenarios when you would break - one, could be that there is a road block / road is broken and two, could be that you have arrived on to your destination. If you have brakes you can see the pothole and stop at the right moment, if not you could get badly injured. Fair enough?Now, you can think of walking on the highway as manual testing, and driving on the highway as automated way of testing. Because, following a certain path is faster if you are in a car. And having the right breaks in your car would help you stop at the right time, saving time - as you could pretty much have the confidence on your breaking system.
• #5: ManishaConfidence also does not come on its own. You would have confidence when you would see it stop you at the right time - when you see it work the right way. So, if we have to list down points that helps build the confidence -- consistencygets used quite oftenTalk about this and relate t
• #6: Shalabh - Test Pyramid – tests at the right levelManisha - Structure / framework – simple / less complexUsing best practicesShalabh - Build suites for different usage by tagging tests and not creating tests for the purposeSmoke / Functions / RegressionManisha - Common understanding about the structure and consumption within the teamShalabh - Have one test for a functionality running on different environment and not multiple test one each for an environment – Android / iOS / WebManisha - Don’t be protective on who would write the test. It need to be a team’s ownership where the right person writes it.
• #7: Shalabh - Consuming the tests on a daily/hourly basisManisha - Run the tests in an automated fashion – no manual triggering the tests