c source control often enough to mind so much what you
use. It's far more important for the committers to pick the tool that works
for them.)
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
on 1.0.8, have_tag and with_tag seem to work
fine on XML for me, so ... if upgrading is an option, might be worth a shot.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
c?
>
Really?
I ran into that with Test::Unit/assert_select, but I was surprised and
pleased to discover that have_tag and with_tag didn't seem to care between
HTML and XML.
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
was having trouble mixing in a module
using include myself, got the same message above, but for a different
method. Not sure if 'include' was having the desired effect for me
(although I found another path by doing the include in "helper.rb" instead
of insid
usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1733:in `top_level'
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1711:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1761:in
`standard_exception_handling'
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake.rb:1708:in `run'
/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/bin/rake:7
/usr/bin/rake:16:in `load'
/usr/bin/rake:16
--
So - the specs are file, but Rake aborted anyway. Thoughts, before I go
a-digging?
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
s far as I can see, "rake spec" doesn't run or report
on my story in stories/filename.rb.
I'm guessing that stuff is still pending, but wanted to confirm before
deciding whether to build something myself or wait for something to come
down.
- Geoffrey
--
Geoffrey Wiseman
___
> `run'
> /usr/lib/ruby/gems/1.8/gems/rspec-1.0.8/lib/spec/runner/command_line.rb:17:in
> `run'
> /usr/lib/ruby/gems/1.8/gems/rspec-1.0.8/bin/spec:3:
> /usr/bin/spec:16:in `load'
> /usr/bin/spec:16:
>
> Finishe
t lead to inconsistent usage. I can live with the
current approach as well, looks odd, but it's not a serious problem for me.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
now? I don't mind trying to diagnose the problem and, if once diagnosed,
look into the effort of creating a patch, but at the moment, I don't even
know why my route generation's failing.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users maili
just spent a while tracking down what I
assumed was a problem in my have_tag only to discover it was a problem with
my with_tag. Just trying to determine if I'm mis-understanding something or
if this is a bug I should file in the tracker?
- Geoffrey
--
Geoffrey Wiseman
__
47app47views47player_containers47show46rhtml'
>
My assumption is that I've done something wrong in RSpec, but I'm not
really sure what; the view seems to work, so as far as I can tell the view
and the route are fine, but the test is not. The error seems to imply the
route shouldn't have an ID, but ... well ... it should, and it does when I
fire up the page in my browser, so I'm not entirely sure why running an
RSpec view spec should get me a different result on a named route
generation.
Suggestions?
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
port of RCov, but do ask on the JRuby list.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
pite the time involved, I'd love to see a written tutorial or screencast
that walks this whole gamut in order if someone ever has time to do one.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On 9/11/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> On 9/11/07, Geoffrey Wiseman <[EMAIL PROTECTED]> wrote:
> > On 9/9/07, Priit Tamboom <[EMAIL PROTECTED]> wrote:
> > > I wonder does anybody planning to go beyond the default html
> > forma
d be nice to be able to use DHTML expansion to see the
source of the spec, sometimes; when we're doing walkthroughs with the
customer representative, it's useful for him to be able to see the source as
well as the descriptions.
- Geoffrey
--
Geoffrey Wiseman
d method `failure_message' for class
`Spec::Matchers::Have'
from
/work/workspace/ng/vendor/plugins/rspec_on_rails/lib/spec/matchers/have.rb:4:in
`alias_method'
from
/work/workspace/ng/vendor/plugins/rspec_on_rails/lib/spec/matchers/have.rb:4
from /usr/local/lib/s
stance without breaking
DRY.
Hadn't really thought about using these just for setup; the syntax would
look a little weird what with it_should_behave_like, but it's still a
thought.
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
On 9/7/07, Pat Maddox <[EMAIL PROTECTED]> wrote:
>
> describe MyModel, " when saved twice" do
>
This is the key point I hadn't considered; makes sense, as long as you make
sure that there's a context wherein the specification that it should have a
certain number of revisions. Thanks!
Realized th
part of the contract that model objects have three revisions, it's just
something I want to make sure is true before I run off and conduct some
tests.
I could raise an exception in the before block if the precondition isn't
met, any other choices?
- Geoffrey
--
Geoffrey Wiseman
ly before, it works just fine.
describe "Customer", "xml" do
fixtures :customers
before do
one = customers(:one)
end
# ...
By design? bug? PEBKAC? Anyone else hit this?
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users
On 9/5/07, David Chelimsky <[EMAIL PROTECTED]> wrote:
>
> > Autotest
> > Out of curiosity, does anyone know how to get autotest to pick up new
> > folders under spec/? Seems like I might have to modify rails_rspec.rb
> in
> > lib/autotest. We were considering separating our acceptance tests from
On 9/5/07, Tor Norbye <[EMAIL PROTECTED]> wrote:
>
> I'm working on Ruby support for NetBeans, and we're bundling RSpec
> (along with JRuby).
Would be pleased to try NB/Ruby again once the RSpec support is in there;
any idea which milestone would contain th
der spec/? Seems like I might have to modify rails_rspec.rb in
lib/autotest. We were considering separating our acceptance tests from the
rest.
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
see if, in a few months, I'm
still missing this feature and, if so, I'll have good RSpec examples in
hand, with which to discuss. ;)
- Geoffrey
--
Geoffrey Wiseman
___
rspec-users mailing list
rspec-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/rspec-users
ronger in RSpec, and I'm in favour of
that. However, I find that often test failures involve unexpected changes (
e.g. the REST service didn't return a status code of 201, as you expected,
because a validation rule changed and the validation failed), which aren't
as easy to message
he model validation fails, I know /why/. I don't see
an easy way to include these sorts of messages in RSpec, which seems likely
to cause me to waste time on test failures. Am I missing something? How
are experienced RSpec users resolving this?
Thanks,
-
26 matches
Mail list logo
