Skip to content

INSTRUCTIONS.md

Latest commit

 

History

History
135 lines (99 loc) · 4.59 KB

INSTRUCTIONS.md

File metadata and controls

135 lines (99 loc) · 4.59 KB

[back/ddd/cqrs] Vehicle fleet parking management

Instructions

I have a vehicle fleet, and I want to manage where every vehicle is parked.

Step 1

register_vehicle.feature

Feature: Register a vehicle

    In order to follow many vehicles with my application
    As an application user
    I should be able to register my vehicle

    @critical
    Scenario: I can register a vehicle
        Given my fleet
        And a vehicle
        When I register this vehicle into my fleet
        Then this vehicle should be part of my vehicle fleet

    Scenario: I can't register same vehicle twice
        Given my fleet
        And a vehicle
        And I have registered this vehicle into my fleet
        When I try to register this vehicle into my fleet
        Then I should be informed this this vehicle has already been registered into my fleet

    Scenario: Same vehicle can belong to more than one fleet
        Given my fleet
        And the fleet of another user
        And a vehicle
        And this vehicle has been registered into the other user's fleet
        When I register this vehicle into my fleet
        Then this vehicle should be part of my vehicle fleet

park_vehicle.feature

Feature: Park a vehicle

    In order to not forget where I've parked my vehicle
    As an application user
    I should be able to indicate my vehicle location

    Background:
        Given my fleet
        And a vehicle
        And I have registered this vehicle into my fleet

    @critical
    Scenario: Successfully park a vehicle
        And a location
        When I park my vehicle at this location
        Then the known location of my vehicle should verify this location

    Scenario: Can't localize my vehicle to the same location two times in a row
        And a location
        And my vehicle has been parked into this location
        When I try to park my vehicle at this location
        Then I should be informed that my vehicle is already parked at this location

Definitions:

  • Vehicle: a car, truck, motorcycle, or any transportation mode that can help me to move from point A to point B on planet earth.
  • Fleet: a collection a distinct vehicles.
  • Location: a way to localize on planet earth, such as GPS coordinates for example.

Guidelines

  1. Do not use any framework at this step!
  2. Prefer not using any production dependency (therefore, for javascript ramda and/or lodash can be used)
  3. Write corresponding bdd tests (behat, cucumber.js, ...)
  4. Your code should resides into the following directory structure:

Bonus

We use Domain Driven Design (DDD) and encourage its application, but all architectures are acceptable for this test.

./src/
   App    # Command, Queries and their handlers
   Domain # Domain models/structures and value objects
          # (classes or structures & functions if FP)
   Infra  # Implementations of repositories and all infrastructure-specific logic

Tips

  • Start by writing Behavior Driven Development (BDD)/Gherkin tests before implementing code.
  • Ask yourself: how many entities do I have?
  • Ask yourself: how many Commands? Queries?
  • At this stage, you don't need to persist data anywhere other than in memory.
  • Here's an indication of the expected number of line of codes for implementations in PHP and JavaScript:

Step 2

Now we want to expose our work to the world! Please wrap Part 1 into a complete application. We want:

  1. A command-line CLI with the following commands:
./fleet create <userId> # returns fleetId on the standard output
./fleet register-vehicle <fleetId> <vehiclePlateNumber>
./fleet localize-vehicle <fleetId> <vehiclePlateNumber> lat lng [alt]
  1. Persistence of fleets and vehicles in a real repository/database.

Guidelines

  1. Feel free to use frameworks/libraries to manage the CLI.
  2. Consider your BDD tool's features (i.e., profiles, suites, tags) to selectively run tests that require real infrastructure (e.g., persistence), while keeping non-critical tests as they were.

Step 3 (Bonus)

  • For code quality, you can use tools — name one or more and briefly explain why.
  • You may consider setting up a CI/CD process — describe the necessary steps briefly.

Evaluation

  • Code quality
  • Avoid over-engineering!
  • Use of good practices and modern programming language features