Ruby on Rails
Monday, September 11, 2017
Thanks, so the testing database is used for unit testing (and I don't have to worry about creating it/emptying as rails does this for me?). I guess I was talking about integration testing, witch sounds like what people mean when they talk about staging. Ive previously worked in telecoms doing Oracle DB development. There they talked about integration testing, performance testing and unit testing.
This is the first time ive taken something from development to production myself. What I have currently is a single public page (based on a view) and some almost vanilla scaffold created screens. They set up configuration (XML feeds etc.) for a bunch of load scripts, that were writern previously in ruby (before I started looking at rails). Also devise to protest them.
The plan is to get it up as a proof of concept so people can look at it then start looking at testing in detail.
Thanks everyone for taking the time to reply, it is really appreciated.
On Sunday, September 10, 2017 at 8:04:20 PM UTC+1, Norbert Melzer wrote:
-- This is the first time ive taken something from development to production myself. What I have currently is a single public page (based on a view) and some almost vanilla scaffold created screens. They set up configuration (XML feeds etc.) for a bunch of load scripts, that were writern previously in ruby (before I started looking at rails). Also devise to protest them.
The plan is to get it up as a proof of concept so people can look at it then start looking at testing in detail.
Thanks everyone for taking the time to reply, it is really appreciated.
On Sunday, September 10, 2017 at 8:04:20 PM UTC+1, Norbert Melzer wrote:
On 09/10/2017 08:33 PM, Ben Edwards wrote:
> Sorry 'git checkout test'. I have develop, test and master branches.
> When I am ready to test for a release I merge develop into test. Cant
> see how I don't want to be in test branch for testing or am I doing
> this all wrong.
This sounds like a concept known as "staging".
Testing usually means having small pieces of code called unit-tests or
specs, which do test your code automatically.
Those tests are written iteratively and close in time to the code they
are testing and usually run in an environment similar to the
dev-environment.
The "staging" concept though, does run the same tests and optionally
additional manual tests, scripted or not, in an environment that is as
close as possible to the actual production environment. Hardware,
operating system, even the smallest system library version should be
identical to the prod environment.
Usually also some stresstrests are made in this environment to ensure
the application is capable to manage the expected load (or even more).
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/daf196d4-0c3a-44b1-83ee-59c47dc2e9a4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment