Hi everyone,
I'm quite new to RSpec, and I have used it mainly for unit-testing. Lately,
a need for a small number of end-to-end tests became relevant. When writing
test-cases, I'm trying to stub all dependencies, but because that's not an
option when doing integration tests, I need some help to understand what's
the proper way to do things. Here's couple of questions:
1. The test requires an IP for remote machine (which is not local and sadly
can not be). Obviously, I shouldn't supply the IP inside the spec file. The
simple way is reading an external YML file with the IP (that will get
created automatically during the CI process with the right IP for example)
and populate the IP directly from it. But, I was checking couple of big
project that uses rspec, and I never seen an external configuration file,
so I'm thinking perhaps there is a better way of doing it
2. If indeed YML file is the right answer, I'm not sure if reading from the
YML file every spec file (that uses this service) is the right thing to do?
Shouldn't I be using hooks instead for that?
3. The test-object is a REST service, and some of the requests require big
json object. I have two options:
a. I can create the json object in the spec file itself (which makes
all information visible to you from the spec file itself, but clutters the
spec)
b. Creating an external default fixture (which is basically a json
file), read from it during the spec, and re-write the values that are
relevant for the specific tests.
Thank you!
--
You received this message because you are subscribed to the Google Groups
"rspec" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/rspec/61ac9ade-1045-4211-80d3-441ef01ae7cb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
