Databases
StackOverflow2013
Postsdbo
PORails error in test driven development
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PORails error in test driven development
    primarykey
    data
    text
    <p>I am following the tutorial of <a href="http://ruby.railstutorial.org" rel="nofollow">Michael Harlt</a> .And i am a newbie of web development.</p> <p>SO i am facing many error while writing test . I am sharing the errors log and i have searched a on internet and looked a lot toward my code but not getting what is the error so please help me i am sharing both the code and the error log. <br> Code of spec file.`</p> <pre><code>require 'spec_helper' describe "Static pages" do subject{ page } describe "Home page" do before {visit root_path} it { should have_selector('h1', text: 'Sample App')} it {should have_selector ('title', text: full_title(''))} it { should_not have_selector 'title', text: '|Home'} end describe "Help page" do before {visit help_path} it { should have_selector('h1', text:'Help')} it { should have_selector('title', text: full_title('Help'))} end describe "About page"do before {visit about_path} it {should have_selector('h1', text:'About')} it {should have_selector('title', text: full_title('About US'))} end describe "Contact page" do before { visit contact_path} it {should have_selector('h1', text:'Contact')} it{should have_selector('title', text: full_title('Contact'))} end end </code></pre> <p>Code for the methode <code>full_title()</code> <br></p> <pre><code> module ApplicationHelper def full_title(page_title) base_title="Ruby on Rails Tutorial Sample App" if page_title.empty? base_title else "#{base_title} | #{page_title} " end end end </code></pre> <p>And the error log is</p> <p>after executing command bundle exec rspec spec/requests/static_pages_spec.rb</p> <p><code>it {should have_selector('title',title: full_title(''))} ^</code></p> <p><strong>C:/sample_app/spec/request/static_pages_spec.rb:15 syntax error,unexpected keyword_end,expecting '}'</strong><br> <strong>**C:/sample_app/spec/request/static_pages_spec.rb:15 syntax error,unexpected keyword_end,expecting '}'**</strong></p> <p><br>spec_helper file for @spullen</p> <pre><code>require 'spec_helper' describe StaticPagesHelper do pending "add some examples to (or delete) #{__FILE__}" end </code></pre>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USjahanzaib kk
    1. USjahanzaib kk
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COIndenting code is quite easy, and crucial in understanding it. Please take a few minutes to indent and outdent appropriately so we (and you) can see what is going on without undue mental load to remember dos and ends.
      singulars
      1. PORails error in test driven development
      1. UScoreyward
    2. COWhat's the error? What does your spec_helper look like? If `full_title` that's the problem after `require 'spec_helper'` add include ApplicationHelper to see if it fixes it.
      singulars
      1. PORails error in test driven development
      1. USspullen
    3. CO@spullen i am sharing the spec_helper wait
      singulars
      1. PORails error in test driven development
      1. USjahanzaib kk
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload