Test "should create a new task and render it on the board" do ![]() Test "should render a new task creation form" do This then tells you need a controller, and some tests for it: describe "BoardController.show" do Now, obviously this is pseudocode, but it gives you the idea of what you're looking to build from the outside, at the browser layer. ![]() fill_in("title").with("Allow users to create new tasks")Īssert Task.where(stage = "Column 2") = 1 That immediately guides us to a testable user story that looks something like the following from the browser layer: Browser So in the Trello clone example, we'd start with the fact that we have columns representing stages, that we need to be able to move cards, representing tasks in the browser. Outside in contrast, would start with the UI or API interactions. Rather it's your prior thoughts/intuition guiding it, with tests being put in post hoc in order to ensure future confidence. As an early career engineer however, this may not be as obvious because they haven't done this hundreds of times.Īs you can also see, this isn't something where your tests are guiding your design. Which would lead to the creation of tests hat looks something like: task = Task.create(params)Īs an experienced engineer it's easy enough to recall and intuit all of these. This would likely result in you creating a schema that looks something like this, with the appropriate migrations.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |