Skip to content

Commit

Permalink
Fixed markdown format for Walkthrough page
Browse files Browse the repository at this point in the history
In order to be supported by GitHub we need to add spaces after `#`
  • Loading branch information
pftg authored and shoe committed Oct 9, 2018
1 parent 2d7448d commit 981de4d
Showing 1 changed file with 4 additions and 4 deletions.
8 changes: 4 additions & 4 deletions docs/walkthrough.md
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
#A Capybara-UI Walkthrough
# A Capybara-UI Walkthrough
Capybara-UI might best be thought of as three layers.

ROLES, that perform => TASKS, which manipulate => ELEMENTS
Expand All @@ -21,7 +21,7 @@ end
You can start to see in the expect statement that Capybara-UI is magical, too.


##Roles
## Roles
A Capybara-UI role groups tasks and elements together, and is defined as a class.
See the [setting up roles](https://github.com/mojotech/capybara-ui/wiki/Setting-Up-Roles) section in the wiki for more how-to ideas.

Expand All @@ -32,7 +32,7 @@ end
```


##Tasks
## Tasks
A task is just a method on a role.

```ruby
Expand All @@ -50,7 +50,7 @@ end
```


##Elements
## Elements
Elements are where the Capybara-UI amazingness begins, as well as where the Capybara-UI confusion heats up. Elements are dom abstractions that allow for precise testing. By using dom element attributes we can easily create the most basic Capybara-UI Element, a widget.

```ruby
Expand Down

0 comments on commit 981de4d

Please sign in to comment.