similar to: How to run stories with `spec'' command?

Hi all, My problem is that I''ve installed both ruby 1.8 (as ruby) and ruby 1.9 (as ruby1.9) on my system. I use spec/rake/spectask for my Rakefile. But the generated command is ruby -I.. blabla it should be "ruby1.9 -I... blabla", but after look at the code of spectask.rb, I found this line: ==> cmd = "ruby " rb_opts = ruby_opts.clone

Hey guys, just poppin in to ask if anyone knows when stories will be somewhat stable? We''re starting to use integration tests at work, we''re already using rspec, and I''d like to avoid integration tests if possible. Thanks, Nate "fowlduck" Sutton

Hi, How can I have a common set of steps that all my stories share? i.e. My stories often start out looking like this: Given a user Joe Given a user Jordan then: Given("a user $username") do |username| @users ||= {} @user_sessions ||= {} @users[username] = create_user(:username => username) @user_sessions[username] = login_as(@users[username]) end I want to share that

I have played a bit with RSpec specs and now want to check out stories. I note that there is no generator for rspec stories pre se (unless I managed to miss all references to one ) and that the only directory relating to stories added by installing rspec is ./stories itself. The documentation at rspec.info seems to presume a great deal of prior knowledge. What I am looking for is a guided tour

hello there, i have been trying my hand at this rbehave material, specifically in terms of integration testing a rails application, and i am curious about the most friendly way to deal with session data. currently, the only way i have found to simulate a session is to open a session and refer to everything afterward via the @session variable stored after open_session. it seems to be workable,

Hi all! Just wrote a few stories and committed code to a project of mine, then realized I made a mistake (with the commit, not the code or tests). It would be nice to put the script that runs the stories as a pre-commit hook, preventing the commit from succeeding if the stories fail. For that, I need to set the right exit code. In turn, I need to know he result of the tests. Given the

Hi, I am confused (a normal state for me) about the State-Of-The-Art Story API to use. examples/calculator.rb has one syntax, the Blogs have another Syntax, so do the various tutorials. I realize that Stories are ongoing work, but it would be nice if there were something I could refer to to make sure that I am not using a syntax that will soon be deprecated, and that I am doing "what is

I''ve been thinking about the structure of the rspec story stuff, and I''ve come up with this for my first post: stories/ # top level to contain all of our story related stuff stories/helper.rb # top level helper stories/helpers/ # other helpers like custom matchers and other libs stories/steps/ # steps go here stories/features/ # top level for features

I have non non-plain-text story without any steps_for, can it be run? If so, how? Thanks, Nate

Hi all, Are there any plans for better documentation for the new StoryRunner feature? I tried to use it today (with Rails), and had a hard time getting my head around whether I was doing it "right" and exactly what things are appropriate to test at that level (this might be exacerbated by the fact that I''ve never really used integration testing that much). A full example of

Hi, I''ve been following this thread and I can get the example stories to run with the ruby command. But I''ve been unable to get the example from http://blog.davidchelimsky.net/articles/2007/10/25/plain-text-stories-part-iii to run with all.rb ruby stories/all.rb /home/edh/story/stories/additions/steps/addition_steps.rb:2: undefined method `steps_for'' for main:Object

I find myself doing this: Scenario "logged in user visiting the home page" do Given "A logged in user" do a_logged_in_user end When "..." Then "..." end The a_logged_in_user method is a helper method in helper.rb which sets up the state so that the user can browse the website. Later in the story of course, I can just do ''Given

> diff --git a/hw/virtio/virtio-pstore.c b/hw/virtio/virtio-pstore.c > new file mode 100644 > index 0000000..b8fb4be > --- /dev/null > +++ b/hw/virtio/virtio-pstore.c > @@ -0,0 +1,699 @@ > +/* > + * Virtio Pstore Device > + * > + * Copyright (C) 2016 LG Electronics > + * > + * Authors: > + * Namhyung Kim <namhyung at gmail.com> > + * > + * This

> diff --git a/hw/virtio/virtio-pstore.c b/hw/virtio/virtio-pstore.c > new file mode 100644 > index 0000000..b8fb4be > --- /dev/null > +++ b/hw/virtio/virtio-pstore.c > @@ -0,0 +1,699 @@ > +/* > + * Virtio Pstore Device > + * > + * Copyright (C) 2016 LG Electronics > + * > + * Authors: > + * Namhyung Kim <namhyung at gmail.com> > + * > + * This

hello, I want to iterate through a list of names and use each element as an argument in a function. For instance: > a = c('one','two','three') > data= c() > for(elem in a){data=cbind(elem = 2,data)} > data elem elem elem [1,] 2 2 2 instead I want 'elem' to be substituted by the string in the list. Doing it by hand would be: > data =

Hello, On Mon, Jul 18, 2016 at 11:03:53AM +0100, Stefan Hajnoczi wrote: > On Mon, Jul 18, 2016 at 01:37:40PM +0900, Namhyung Kim wrote: > > +static void virtio_pstore_handle_io(VirtIODevice *vdev, VirtQueue *vq) > > +{ > > + VirtIOPstore *s = VIRTIO_PSTORE(vdev); > > + VirtQueueElement *elem; > > + struct virtio_pstore_hdr *hdr; > > + ssize_t

Hello, On Mon, Jul 18, 2016 at 11:03:53AM +0100, Stefan Hajnoczi wrote: > On Mon, Jul 18, 2016 at 01:37:40PM +0900, Namhyung Kim wrote: > > +static void virtio_pstore_handle_io(VirtIODevice *vdev, VirtQueue *vq) > > +{ > > + VirtIOPstore *s = VIRTIO_PSTORE(vdev); > > + VirtQueueElement *elem; > > + struct virtio_pstore_hdr *hdr; > > + ssize_t

I have been trying to write a selector function for Autocompleter.Local that will show a predefined Array and will scroll automatically to the first match. I have had success with with getting my list to populate and show all of the choices, however I cannot get it to scroll to the first match. Since I build the JS Array I can know exactly how many items are in the list going into my selector,

Check for a "product.id" file in an architecture-specific subdirectory of the main partition, and use its data to improve the data on the media. Only Mageia as distribution name is recognized there, since most probably this file will not be available on other distros. --- Changes in v2: - simplify file reading using guestfs_int_first_line_of_file lib/inspect-fs-cd.c | 62

Check for a "product.id" file in an architecture-specific subdirectory of the main partition, and use its data to improve the data on the media. Only Mageia as distribution name is recognized there, since most probably this file will not be available on other distros. --- lib/inspect-fs-cd.c | 76 +++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 76 insertions(+)