Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>First of all, you need to arrange for the <code>proxy</code> method to return a proxy in one test case and not in the other. If there is a "setter" method for proxy, you can use that, otherwise you can stub the <code>proxy</code> method.</p> <p>Then, at a minimum, you want to set an expectation on <code>open</code> that it will be called with or without the <code>:proxy</code> option, depending on which test it is. Beyond that, you have the choice of whether to stub and set expectations for the various other calls involved in the method, including <code>URI.parse</code> and <code>Nokogiri::HTML</code>.</p> <p>See <a href="https://github.com/rspec/rspec-mocks" rel="nofollow noreferrer">https://github.com/rspec/rspec-mocks</a> for information on establishing your test doubles and setting expectations. Note in particular the <code>and_call_original</code> option if you want to use a partial stubbing approach.</p> <p>Update: Here's some code to get you started. This works for the non-proxy method. I've left the proxy case for you. Note also that this uses the "partial stubbing" approach, where you still end up calling the external gems.</p> <pre><code>require 'spec_helper' describe MyClass do describe '.proxy' do # NOTE: This test succeeds because of attr_accessor, but you're calling a MyClass.proxy (a class method) within your page_content method it { should respond_to(:proxy) } end describe '.page_content' do let(:url) { "https://google.com/" } let(:page_content) { MyClass.page_content(url) } # NOTE: Changed to invoke class method context 'when not using a proxy' do before {allow(MyClass).to receive(:proxy).and_return(false)} # Stubbed for no-proxy case it 'returns a Nokogiri::HTML::Document' do page_content.should be_a(Nokogiri::HTML::Document) end it 'should not set open-uri proxy properties' do expect(MyClass).to receive(:open).with(url).and_call_original # Stubbing open is tricky, see note afterwards page_content end end # How do i test this method actually uses a proxy when it's set vs not set? context 'when using a proxy' do # ??? xit 'should set open-uri proxy properties' do end end end end </code></pre> <p>Stubbing of <code>open</code> is tricky. See <a href="https://stackoverflow.com/questions/10796986/how-to-rspec-mock-open-uri/11258596#11258596">How to rspec mock open-uri?</a> for an explanation.</p>
    singulars
    1. This table or related slice is empty.
    1. POHow do I test this particular method?
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USCommunity
    1. USPeter Alfvin
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POHow do I test this particular method?
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTAcceptedByOriginator
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI have updated my question to show there is an `attr_accessor` for `proxy`. Your first paragraph makes sense; thank you. What you said about using mocks and `and_call_original` does not make sense, unfortunately. I have actually read the documentation and skimmed the rspec book but i'm having trouble understanding what objects to mock and would love to see code if possible. thank you!
      singulars
      1. PO
      1. USCharlesHorse
    2. CO`attr_accessor` gives you setters and getters for *instance variables*. You're referencing `proxy` via a class method by the same name.
      singulars
      1. PO
      1. USPeter Alfvin
    3. COYou've also defined `page_content` to be `subject.page_content(...)`, but `subject` is implicitly a new *instance* of `MyClass` and there is no `page_content` instance method. In general, if you start executing your spec, RSpec will tell you what you've gotten wrong and if you get stuck, you can get help here.
      singulars
      1. PO
      1. USPeter Alfvin
 

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