During my time as a test engineer, I came face to face with the philosophical horror that lies at the heart of test d̴̫̞̊ẹ̷̜̲͑̑v̶̩̲̒̾͌e̵̳̯̜͌̚͝ḻ̴̻̰̿o̸͍̍̂̐͊p̶̺͒̒́̐m̴̪͇̳͎̺̩̥̀̈̇̆́̄͗͜e̴̡̢͚̣̬̣̞̩̥͈̟͖͔͑̌͐̈́̂̓̀̎̐̚͝ņ̸̧̨̢̛̛̯͍̘̙̲͖̯̖͈̳͕̮͖͔̹̬̀̏̾̉̄̐̽̔̍̊̓͌̏͗͛͘͜͜͝ţ̵̢̢̨̢̳̪͓͙̹͈̪̝͍̱̹̟̥̥̣̲̹͎̬͔͒͑̽͐͜͝. 

s̶̡͍̹͕͈̼͈̰̹͈̩͇̟̾̿̅e̵͈̳͂́̇̌̓̀̊̏̍̔̀̈́̽̌̅̚͝ṫ̸̢̧̺̘̞̮̥͚̗̻̘͇̌̔̈͗̋̎̑̂̓̆̊̈́̿̎̏̐̆ ő̶͎̠f̷̹͒ abstractions required to implement all possible tests. These core abstractions allow for rapid test development and resist the forces of schedule pressure, allowing the test framework to remain cohesive. Over time, as additional requirements are discovered, the test framework consumes and exhausts its core abstractions and begins consuming hacks and patches. This new fuel source cannot provide sufficient cohesion to counteract the effects of schedule pressure, and the t̸̘̫̀ȩ̷͇̋͘s̷̫̉͜t̴̳̎̕ f̷̱̼͔͈̑̌̊͗́̓ȓ̵̹̣̲͍̜̤͊̄̅̌́͆̇͜a̴̦͔̖̅͑͜m̴͙̋͂ę̵͕̝̋͗̄̄́̒̕̚ẁ̵̨̨̛͔̟̪̭̠͖̝̼̥͙̫͎̱͖̰͍̜̭͍̹̯͊̇́̆̇͂͑̿̂̐̃͗̇̀͘͝ͅợ̴̡̣̝͔̖̟̻̫̔̎͋͐̈́͑̈́͊̽͑r̴̛̘̤̀́́͊̋̿͒͊͒̃̀̌͆͊̀̿̈́͒̈́̆̈́̌̐̕͠k̷̢̛̰̝͚̞̻̩̈́̀̌̽̂̀̂͗͌͜

What is a test?

What is a measurement?

What is the point?