Skip to content
Projects
Groups
Snippets
Help
Loading...
Help
Support
Keyboard shortcuts
?
Submit feedback
Contribute to GitLab
Sign in / Register
Toggle navigation
G
gitlab-ce
Project overview
Project overview
Details
Activity
Releases
Repository
Repository
Files
Commits
Branches
Tags
Contributors
Graph
Compare
Issues
0
Issues
0
List
Boards
Labels
Milestones
Merge Requests
1
Merge Requests
1
Analytics
Analytics
Repository
Value Stream
Wiki
Wiki
Snippets
Snippets
Members
Members
Collapse sidebar
Close sidebar
Activity
Graph
Create a new issue
Commits
Issue Boards
Open sidebar
nexedi
gitlab-ce
Commits
88bd5fa2
Commit
88bd5fa2
authored
Oct 12, 2017
by
Clement Ho
Browse files
Options
Browse Files
Download
Email Patches
Plain Diff
Update best_practices.md
parent
77d636cc
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
with
11 additions
and
6 deletions
+11
-6
doc/development/testing_guide/best_practices.md
doc/development/testing_guide/best_practices.md
+11
-6
No files found.
doc/development/testing_guide/best_practices.md
View file @
88bd5fa2
...
...
@@ -267,15 +267,20 @@ RSpec.configure do |config|
end
```
### Debugging
### Debugging
Capybara
If you need to debug Capybara tests, using the following lines,
you can get the current URL of Capybara server, logged in user email. Then you
can add some arbitrary sleep to halt the test and go check out the page.
Sometimes you may need to debug Capybara tests by observing browser behavior.
Default user password is
`12345678`
.
You can stall capybara and view the website on the browser by adding a long sleep command in your spec and then opening your browser
to the capybara url.
```
You can get the capybara url by doing
`puts current_url`
.
You can also get the user's email by doing
`puts user.email`
.
The default password for the user is
`12345678`
.
Example:
```
ruby
puts
current_url
puts
user
.
email
sleep
(
200
)
...
...
Write
Preview
Markdown
is supported
0%
Try again
or
attach a new file
Attach a file
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Cancel
Please
register
or
sign in
to comment