All the XCTFramework methods accepts a last parameter that is a custom message

The code itself is self explanatory, not needing additional arguments

Structuring it hierarchically using Quick

In the Quick/Nimble tests file and in the XCTest tests file, you can find implementations of unit tests that validate a Car object, testing the following scenarios:
- Pressing the start button, if the shift is in the P position and the brake pedal is being pressed the car should start the engine
- Pressing the start button, if the shift is not in the P position the car should not start the engine
- Pressing the start button, if the shift is not in the P position and the brake pedal is not being pressed the car should not start the engine
- Fueling the car, With specific gas price Should fill the correct quantity