This section outlines porting tasks that you need to tackle when you get to the point that you actually build your application against GTK+ 3. Making it possible to prepare for these in GTK+ 2.24 would have been either impossible or impractical.
The request-phase of the traditional GTK+ geometry management
has been replaced by a more flexible height-for-width system,
which is described in detail in the API documentation
(see the section called “Height-for-width Geometry Management”). As a consequence,
the ::size-request signal and vfunc has been removed from
GtkWidgetClass. The replacement for size_request()
can
take several levels of sophistication:
As a minimal replacement to keep current functionality,
you can simply implement the GtkWidgetClass.get_preferred_width()
and
GtkWidgetClass.get_preferred_height()
vfuncs by calling your existing
size_request()
function. So you go from
1 2 3 4 5 6 7 8 9 10 11 |
static void my_widget_class_init (MyWidgetClass *class) { GtkWidgetClass *widget_class = GTK_WIDGET_CLASS (class); /* ... */ widget_class->size_request = my_widget_size_request; /* ... */ } |
to something that looks more like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 |
static void my_widget_get_preferred_width (GtkWidget *widget, gint *minimal_width, gint *natural_width) { GtkRequisition requisition; my_widget_size_request (widget, &requisition); *minimal_width = *natural_width = requisition.width; } static void my_widget_get_preferred_height (GtkWidget *widget, gint *minimal_height, gint *natural_height) { GtkRequisition requisition; my_widget_size_request (widget, &requisition); *minimal_height = *natural_height = requisition.height; } /* ... */ static void my_widget_class_init (MyWidgetClass *class) { GtkWidgetClass *widget_class = GTK_WIDGET_CLASS (class); /* ... */ widget_class->get_preferred_width = my_widget_get_preferred_width; widget_class->get_preferred_height = my_widget_get_preferred_height; /* ... */ } |
Sometimes you can make things a little more streamlined
by replacing your existing size_request()
implementation by
one that takes an orientation parameter:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 |
static void my_widget_get_preferred_size (GtkWidget *widget, GtkOrientation orientation, gint *minimal_size, gint *natural_size) { /* do things that are common for both orientations ... */ if (orientation == GTK_ORIENTATION_HORIZONTAL) { /* do stuff that only applies to width... */ *minimal_size = *natural_size = ... } else { /* do stuff that only applies to height... */ *minimal_size = *natural_size = ... } } static void my_widget_get_preferred_width (GtkWidget *widget, gint *minimal_width, gint *natural_width) { my_widget_get_preferred_size (widget, GTK_ORIENTATION_HORIZONTAL, minimal_width, natural_width); } static void my_widget_get_preferred_height (GtkWidget *widget, gint *minimal_height, gint *natural_height) { my_widget_get_preferred_size (widget, GTK_ORIENTATION_VERTICAL, minimal_height, natural_height); } /* ... */ |
If your widget can cope with a small size,
but would appreciate getting some more space (a common
example would be that it contains ellipsizable labels),
you can do that by making your GtkWidgetClass.get_preferred_width()
/
GtkWidgetClass.get_preferred_height()
functions return a smaller value for minimal
than for natural
.
For minimal
, you probably want to return the same value
that your size_request()
function returned before (since
size_request()
was defined as returning the minimal size
a widget can work with). A simple way to obtain good
values for natural
, in the case of containers, is to use
gtk_widget_get_preferred_width()
and
gtk_widget_get_preferred_height()
on the children of the
container, as in the following example:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
static void gtk_fixed_get_preferred_height (GtkWidget *widget, gint *minimum, gint *natural) { GtkFixed *fixed = GTK_FIXED (widget); GtkFixedPrivate *priv = fixed->priv; GtkFixedChild *child; GList *children; gint child_min, child_nat; *minimum = 0; *natural = 0; for (children = priv->children; children; children = children->next) { child = children->data; if (!gtk_widget_get_visible (child->widget)) continue; gtk_widget_get_preferred_height (child->widget, &child_min, &child_nat); *minimum = MAX (*minimum, child->y + child_min); *natural = MAX (*natural, child->y + child_nat); } } |
Note that the GtkWidgetClass.get_preferred_width()
/
GtkWidgetClass.get_preferred_height()
functions
only allow you to deal with one dimension at a time. If your
size_request()
handler is doing things that involve both
width and height at the same time (e.g. limiting the aspect
ratio), you will have to implement
GtkWidgetClass.get_preferred_height_for_width()
and GtkWidgetClass.get_preferred_width_for_height()
.
To make full use of the new capabilities of the
height-for-width geometry management, you need to additionally
implement the GtkWidgetClass.get_preferred_height_for_width()
and
GtkWidgetClass.get_preferred_width_for_height()
. For details on
these functions, see the section called “Height-for-width Geometry Management”.
Starting with version 1.10, cairo provides a region API that is equivalent to the GDK region API (which was itself copied from the X server). Therefore, the region API has been removed in GTK+ 3.
Porting your application to the cairo region API should be a straight find-and-replace task. Please refer to the following table:
Table 14.
| GDK | cairo |
|---|---|
| GdkRegion | cairo_region_t |
| GdkRectangle | cairo_rectangle_int_t |
gdk_rectangle_intersect() |
this function is still there |
gdk_rectangle_union() |
this function is still there |
gdk_region_new() |
cairo_region_create() |
gdk_region_copy() |
cairo_region_copy() |
gdk_region_destroy() |
cairo_region_destroy() |
gdk_region_rectangle() |
cairo_region_create_rectangle() |
gdk_region_get_clipbox() |
cairo_region_get_extents() |
gdk_region_get_rectangles() |
cairo_region_num_rectangles() and
cairo_region_get_rectangle()
|
gdk_region_empty() |
cairo_region_is_empty() |
gdk_region_equal() |
cairo_region_equal() |
gdk_region_point_in() |
cairo_region_contains_point() |
gdk_region_rect_in() |
cairo_region_contains_rectangle() |
gdk_region_offset() |
cairo_region_translate() |
gdk_region_union_with_rect() |
cairo_region_union_rectangle() |
gdk_region_intersect() |
cairo_region_intersect() |
gdk_region_union() |
cairo_region_union() |
gdk_region_subtract() |
cairo_region_subtract() |
gdk_region_xor() |
cairo_region_xor() |
gdk_region_shrink() |
no replacement |
gdk_region_polygon() |
no replacement, use cairo paths instead |
The GdkPixmap object and related functions have been removed. In the cairo-centric world of GTK+ 3, cairo surfaces take over the role of pixmaps.
Example 41. Creating custom cursors
One place where pixmaps were commonly used is to create custom cursors:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 |
GdkCursor *cursor; GdkPixmap *pixmap; cairo_t *cr; GdkColor fg = { 0, 0, 0, 0 }; pixmap = gdk_pixmap_new (NULL, 1, 1, 1); cr = gdk_cairo_create (pixmap); cairo_rectangle (cr, 0, 0, 1, 1); cairo_fill (cr); cairo_destroy (cr); cursor = gdk_cursor_new_from_pixmap (pixmap, pixmap, &fg, &fg, 0, 0); g_object_unref (pixmap); |
The same can be achieved without pixmaps, by drawing onto an image surface:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
GdkCursor *cursor; cairo_surface_t *s; cairo_t *cr; GdkPixbuf *pixbuf; s = cairo_image_surface_create (CAIRO_FORMAT_A1, 3, 3); cr = cairo_create (s); cairo_arc (cr, 1.5, 1.5, 1.5, 0, 2 * M_PI); cairo_fill (cr); cairo_destroy (cr); pixbuf = gdk_pixbuf_get_from_surface (s, 0, 0, 3, 3); cairo_surface_destroy (s); cursor = gdk_cursor_new_from_pixbuf (display, pixbuf, 0, 0); g_object_unref (pixbuf); |
For drawing with cairo, it is not necessary to allocate colors, and
a GdkVisual provides enough information for cairo to handle colors
in 'native' surfaces. Therefore, GdkColormap and related functions
have been removed in GTK+ 3, and visuals are used instead. The
colormap-handling functions of GtkWidget (gtk_widget_set_colormap()
,
etc) have been removed and gtk_widget_set_visual()
has been added.
Example 42. Setting up a translucent window
You might have a screen-changed handler like the following to set up a translucent window with an alpha-channel:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
static void on_alpha_screen_changed (GtkWidget *widget, GdkScreen *old_screen, GtkWidget *label) { GdkScreen *screen = gtk_widget_get_screen (widget); GdkColormap *colormap = gdk_screen_get_rgba_colormap (screen); if (colormap == NULL) colormap = gdk_screen_get_default_colormap (screen); gtk_widget_set_colormap (widget, colormap); } |
With visuals instead of colormaps, this will look as follows:
1 2 3 4 5 6 7 8 9 10 11 12 13 |
static void on_alpha_screen_changed (GtkWindow *window, GdkScreen *old_screen, GtkWidget *label) { GdkScreen *screen = gtk_widget_get_screen (GTK_WIDGET (window)); GdkVisual *visual = gdk_screen_get_rgba_visual (screen); if (visual == NULL) visual = gdk_screen_get_system_visual (screen); gtk_widget_set_visual (window, visual); } |
GdkDrawable has been removed in GTK+ 3, together with GdkPixmap and GdkImage. The only remaining drawable class is GdkWindow. For dealing with image data, you should use a cairo_surface_t or a GdkPixbuf.
GdkDrawable functions that are useful with windows have been replaced by corresponding GdkWindow functions:
Table 15. GdkDrawable to GdkWindow
| GDK 2.x | GDK 3 |
|---|---|
gdk_drawable_get_visual() |
gdk_window_get_visual() |
gdk_drawable_get_size() |
gdk_window_get_width()
gdk_window_get_height()
|
gdk_pixbuf_get_from_drawable() |
gdk_pixbuf_get_from_window() |
gdk_drawable_get_clip_region() |
gdk_window_get_clip_region() |
gdk_drawable_get_visible_region() |
gdk_window_get_visible_region() |
If your application uses the low-level event filtering facilities in GDK, there are some changes you need to be aware of.
The special-purpose GdkEventClient events and the gdk_add_client_message_filter()
and gdk_display_add_client_message_filter()
functions have been
removed. Receiving X11 ClientMessage events is still possible, using
the general gdk_window_add_filter()
API. A client message filter like
1 2 3 4 5 6 7 8 9 10 11 12 |
static GdkFilterReturn message_filter (GdkXEvent *xevent, GdkEvent *event, gpointer data) { XClientMessageEvent *evt = (XClientMessageEvent *)xevent; /* do something with evt ... */ } ... message_type = gdk_atom_intern ("MANAGER", FALSE); gdk_display_add_client_message_filter (display, message_type, message_filter, NULL); |
then looks like this:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 |
static GdkFilterReturn event_filter (GdkXEvent *xevent, GdkEvent *event, gpointer data) { XClientMessageEvent *evt; GdkAtom message_type; if (((XEvent *)xevent)->type != ClientMessage) return GDK_FILTER_CONTINUE; evt = (XClientMessageEvent *)xevent; message_type = XInternAtom (evt->display, "MANAGER", FALSE); if (evt->message_type != message_type) return GDK_FILTER_CONTINUE; /* do something with evt ... */ } ... gdk_window_add_filter (NULL, message_filter, NULL); |
One advantage of using an event filter is that you can actually
remove the filter when you don't need it anymore, using
gdk_window_remove_filter()
.
The other difference to be aware of when working with event filters
in GTK+ 3 is that GDK now uses XI2 by default when available. That
means that your application does not receive core X11 key or button
events. Instead, all input events are delivered as XIDeviceEvents.
As a short-term workaround for this, you can force your application
to not use XI2, with gdk_disable_multidevice()
. In the long term,
you probably want to rewrite your event filter to deal with
XIDeviceEvents.
In GTK+ 2.x, GDK could only be compiled for one backend at a time,
and the GDK_WINDOWING_X11
or GDK_WINDOWING_WIN32
macros could
be used to find out which one you are dealing with:
1 2 3 4 5 6 7 |
#ifdef GDK_WINDOWING_X11 if (timestamp != GDK_CURRENT_TIME) gdk_x11_window_set_user_time (gdk_window, timestamp); #endif #ifdef GDK_WINDOWING_WIN32 /* ... win32 specific code ... */ #endif |
In GTK+ 3, GDK can be built with multiple backends, and currently used backend has to be determined at runtime, typically using type-check macros on a GdkDisplay or GdkWindow. You still need to use the GDK_WINDOWING macros to only compile code referring to supported backends:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
#ifdef GDK_WINDOWING_X11 if (GDK_IS_X11_DISPLAY (display)) { if (timestamp != GDK_CURRENT_TIME) gdk_x11_window_set_user_time (gdk_window, timestamp); } else #endif #ifdef GDK_WINDOWING_WIN32 if (GDK_IS_WIN32_DISPLAY (display)) { /* ... win32 specific code ... */ } else #endif { g_warning ("Unsupported GDK backend"); } |
If you used the pkg-config variable target
to
conditionally build part of your project depending on the GDK backend,
for instance like this:
1 |
AM_CONDITIONAL(BUILD_X11, test `$PKG_CONFIG --variable=target gtk+-2.0` = "x11") |
then you should now use the M4 macro provided by GTK+ itself:
1 2 |
GTK_CHECK_BACKEND([x11], [3.0.2], [have_x11=yes], [have_x11=no]) AM_CONDITIONAL(BUILD_x11, [test "x$have_x11" = "xyes"]) |
The GtkPlug and GtkSocket widgets are now X11-specific, and you
have to include the <gtk/gtkx.h>
header
to use them. The previous section about proper handling of
backend-specific code applies, if you care about other backends.
The GtkWidget “expose-event” signal has been replaced by a new “draw” signal, which takes a cairo_t instead of an expose event. The cairo context is being set up so that the origin at (0, 0) coincides with the upper left corner of the widget, and is properly clipped.
In other words, the cairo context of the draw signal is set up in 'widget coordinates', which is different from traditional expose event handlers, which always assume 'window coordinates'.
The widget is expected to draw itself with its allocated size, which
is available via the new gtk_widget_get_allocated_width()
and
gtk_widget_get_allocated_height()
functions. It is not necessary to
check for gtk_widget_is_drawable()
, since GTK+ already does this check
before emitting the “draw” signal.
There are some special considerations for widgets with multiple windows. Expose events are window-specific, and widgets with multiple windows could expect to get an expose event for each window that needs to be redrawn. Therefore, multi-window expose event handlers typically look like this:
1 2 3 4 5 6 7 8 9 |
if (event->window == widget->window1) { /* ... draw window1 ... */ } else if (event->window == widget->window2) { /* ... draw window2 ... */ } ... |
In contrast, the “draw” signal handler may have to draw multiple
windows in one call. GTK+ has a convenience function
gtk_cairo_should_draw_window()
that can be used to find out if
a window needs to be drawn. With that, the example above would look
like this (note that the 'else' is gone):
1 2 3 4 5 6 7 8 9 |
if (gtk_cairo_should_draw_window (cr, widget->window1) { /* ... draw window1 ... */ } if (gtk_cairo_should_draw_window (cr, widget->window2) { /* ... draw window2 ... */ } ... |
Another convenience function that can help when implementing
::draw for multi-window widgets is gtk_cairo_transform_to_window()
,
which transforms a cairo context from widget-relative coordinates
to window-relative coordinates. You may want to use cairo_save()
and
cairo_restore()
when modifying the cairo context in your draw function.
All GtkStyle drawing functions (gtk_paint_box()
, etc) have been changed
to take a cairo_t instead of a window and a clip area. ::draw
implementations will usually just use the cairo context that has been
passed in for this.
Example 43. A simple ::draw function
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 |
gboolean gtk_arrow_draw (GtkWidget *widget, cairo_t *cr) { GtkStyleContext *context; gint x, y; gint width, height; gint extent; context = gtk_widget_get_style_context (widget); width = gtk_widget_get_allocated_width (widget); height = gtk_widget_get_allocated_height (widget); extent = MIN (width - 2 * PAD, height - 2 * PAD); x = PAD; y = PAD; gtk_render_arrow (context, rc, G_PI / 2, x, y, extent); } |
In GTK+ 2.x, GtkProgressBar and GtkCellRendererProgress were using the
GtkProgressBarOrientation enumeration to specify their orientation and
direction. In GTK+ 3, both the widget and the cell renderer implement
GtkOrientable, and have an additional 'inverted' property to determine
their direction. Therefore, a call to gtk_progress_bar_set_orientation()
needs to be replaced by a pair of calls to
gtk_orientable_set_orientation()
and gtk_progress_bar_set_inverted()
.
The following values correspond:
Table 16.
| GTK+ 2.x | GTK+ 3 | |
|---|---|---|
| GtkProgressBarOrientation | GtkOrientation | inverted |
| GTK_PROGRESS_LEFT_TO_RIGHT | GTK_ORIENTATION_HORIZONTAL | FALSE |
| GTK_PROGRESS_RIGHT_TO_LEFT | GTK_ORIENTATION_HORIZONTAL | TRUE |
| GTK_PROGRESS_TOP_TO_BOTTOM | GTK_ORIENTATION_VERTICAL | FALSE |
| GTK_PROGRESS_BOTTOM_TO_TOP | GTK_ORIENTATION_VERTICAL | TRUE |
The behaviour of expanding widgets has changed slightly in GTK+ 3,
compared to GTK+ 2.x. It is now 'inherited', i.e. a container that
has an expanding child is considered expanding itself. This is often
the desired behaviour. In places where you don't want this to happen,
setting the container explicity as not expanding will stop the
expand flag of the child from being inherited. See
gtk_widget_set_hexpand()
and gtk_widget_set_vexpand()
.
If you experience sizing problems with widgets in ported code, carefully check the GtkBox expand and GtkBox fill child properties of your boxes.
The default values for the “hscrollbar-policy” and “vscrollbar-policy” properties have been changed from 'never' to 'automatic'. If your application was relying on the default value, you will have to set it explicitly.
The ::set-scroll-adjustments signal on GtkWidget has been replaced by the GtkScrollable interface which must be implemented by a widget that wants to be placed in a GtkScrolledWindow. Instead of emitting ::set-scroll-adjustments, the scrolled window simply sets the “hadjustment” and “vadjustment” properties.
GtkObject has been removed in GTK+ 3. Its remaining functionality, the ::destroy signal, has been moved to GtkWidget. If you have non-widget classes that are directly derived from GtkObject, you have to make them derive from GInitiallyUnowned (or, if you don't need the floating functionality, GObject). If you have widgets that override the destroy class handler, you have to adjust your class_init function, since destroy is now a member of GtkWidgetClass:
1 2 3 |
GtkObjectClass *object_class = GTK_OBJECT_CLASS (class); object_class->destroy = my_destroy; |
becomes
1 2 3 |
GtkWidgetClass *widget_class = GTK_WIDGET_CLASS (class); widget_class->destroy = my_destroy; |
In the unlikely case that you have a non-widget class that is derived from GtkObject and makes use of the destroy functionality, you have to implement ::destroy yourself.
If your program used functions like gtk_object_get or gtk_object_set, these can be replaced directly with g_object_get or g_object_set. In fact, most every gtk_object_* function can be replaced with the corresponding g_object_ function, even in GTK+ 2 code. The one exception to this rule is gtk_object_destroy, which can be replaced with gtk_widget_destroy, again in both GTK+ 2 and GTK+ 3.
The “match-selected” and “cursor-on-match” signals were erroneously given the internal filter model instead of the users model. This oversight has been fixed in GTK+ 3; if you have handlers for these signals, they will likely need slight adjustments.
The resize grip functionality has been moved from GtkStatusbar
to GtkWindow. Any window can now have resize grips, regardless whether
it has a statusbar or not. The functions
gtk_statusbar_set_has_resize_grip()
and gtk_statusbar_get_has_resize_grip()
have disappeared, and instead there are now
gtk_window_set_has_resize_grip()
and gtk_window_get_has_resize_grip()
.
In more recent versions of GTK+ 3, the resize grip functionality has been removed entirely, in favor of invisible resize borders around the window. When updating to newer versions of GTK+ 3, you should simply remove all code dealing with resize grips.
Linking against GTK+ 2.x and GTK+ 3 in the same process is problematic
and can lead to hard-to-diagnose crashes. The gtk_init()
function in
both GTK+ 2.22 and in GTK+ 3 tries to detect this situation and abort
with a diagnostic message, but this check is not 100% reliable (e.g. if
the problematic linking happens only in loadable modules).
Direct linking of your application against both versions of GTK+ is easy to avoid; the problem gets harder when your application is using libraries that are themselves linked against some version of GTK+. In that case, you have to verify that you are using a version of the library that is linked against GTK+ 3.
If you are using packages provided by a distributor, it is likely that parallel installable versions of the library exist for GTK+ 2.x and GTK+ 3, e.g for vte, check for vte3; for webkitgtk look for webkitgtk3, and so on.
Some software packages install loadable GTK+ modules such as theme engines,
gdk-pixbuf loaders or input methods. Since GTK+ 3 is parallel-installable
with GTK+ 2.x, the two GTK+ versions have separate locations for their
loadable modules. The location for GTK+ 2.x is
(and its subdirectories), for GTK+ 3 the location is
libdir
/gtk-2.0
(and its subdirectories).
libdir
/gtk-3.0
For some kinds of modules, namely input methods and pixbuf loaders,
GTK+ keeps a cache file with extra information about the modules.
For GTK+ 2.x, these cache files are located in
.
For GTK+ 3, they have been moved to
sysconfdir
/gtk-2.0
.
The commands that create these cache files have been renamed with a -3
suffix to make them parallel-installable.
libdir
/gtk-3.0/3.0.0/
Note that GTK+ modules often link against libgtk, libgdk-pixbuf, etc. If that is the case for your module, you have to be careful to link the GTK+ 2.x version of your module against the 2.x version of the libraries, and the GTK+ 3 version against hte 3.x versions. Loading a module linked against libgtk 2.x into an application using GTK+ 3 will lead to unhappiness and must be avoided.


There are some additional features that you may already discovered about the renderer core engine.
Graphic features
I have always wanted the W3C to add this features to the CSS spec (and so far, not there yet :)
- Gradients on backgrounds
- Rounded corners
And I think many many web designers would agree. Is it so hard or what?.
Background Gradients
It is a simple two color linear gradient, achieved by the adding of two CSS properties:
Some examples
background-gradient: (#Color)
- Second color of the gradient background, the first one is given bybackground-color
. Not inherited.background-gradient-angle: (number)
- Angle (in degrees, clockwise) of the gradient. Not inherited. Initial value:90
0 degrees 45 degrees 90 degrees 135 degrees 180 degrees Rounded corners
As you may already know, CSS is based on a Box Model, where every box has it's own set of properties. Since we are talking abound boxes, why not to make them with rounded corners, almost every website you visit nowadays makes use of rounded corners, where a not very nice trick with images and tables must be used.
In this renderer, the rounded corners are achieved by adding this CSS properties:
Some examples
corner-ne-radius: (length)
Indicates the radius of the north-east corner. Not inerittedcorner-se-radius: (length)
Indicates the radius of the south-east corner. Not inerittedcorner-sw-radius: (length)
Indicates the radius of the south-west corner. Not inerittedcorner-nw-radius: (length)
Indicates the radius of the north-west corner. Not inerittedcorner-radius: (length){1,4}
Shorthand for the other corner properties. Not ineritted
c1 c2 c3 c4 c5 .c1, .c2, .c3, .c4, .c5 { background-color:olive; border:0px; color:white; vertical-align:middle; } .c1 { corner-radius: 0px } .c2 { corner-radius: 10px } .c3 { corner-radius: 0px 10px 10px 0px } .c4 { corner-radius: 18px } .c5 { corner-radius: 10px; border: outset #bb0 2px; }


Hosts set a price that reimburses their grocery costs. Guests pay the hosts when they arrive. Cash and Venmo are the best options.
Find the Mealshare listing on our website. You’ll be able to see who has RSVP’d.
You should expect to meet students from different majors, different years and different backgrounds. Embracing the unique social atmosphere is important to the NÜDL experience.
All NÜDL events are BYOB. Mealshare hosts are asked to provide water for all of their guests.
Typically lasts for about an hour, but sometimes they go longer. Feel free to leave at any point after the dishes have been cleared.
Awkward overload? If anything makes you seriously uncomfortable you can text or call us at<PHONE_NUMBER> or<PHONE_NUMBER>.


3.2.0 Development
Enhancements:
- Improve the
inspect
output of example groups. (Mike Dalton, #1687) - When rake task fails, only output the command if
verbose
flag is set. (Ben Snape, #1704) - Add
RSpec.clear_examples
as a clear way to reset examples in between spec runs, whilst retaining user configuration. (Alexey Fedorov, #1706) - Reduce string allocations when defining and running examples by 70% and 50% respectively. (Myron Marston, #1738)
- Removed dependency on pathname from stdlib. (Sam Phippen, #1703)
- Improve the message presented when a user hits Ctrl-C. (Alex Chaffee #1717, #1742)
- Improve shared example group inclusion backtrace displayed in failed example output so that it works for all methods of including shared example groups and shows all inclusion locations. (Myron Marston, #1763)
- Issue seed notification at start (as well as the end) of the reporter run. (Arlandis Word, #1761)
- Improve the documentation of around hooks. (Jim Kingdon, #1772)
- Support prepending of modules into example groups from config and allow filtering based on metadata. (Arlandis Word, #1806)
- Emit warnings when
:suite
hooks are registered on an example group (where it has always been ignored) or are registered with metadata (which has always been ignored). (Myron Marston, #1805) - Provide a friendly error message when users call RSpec example group
APIs (e.g.
context
,describe
,it
,let
,before
, etc) from within an example where those APIs are unavailable. (Myron Marston, #1819) - Provide a friendly error message when users call RSpec example
APIs (e.g.
expect
,double
,stub_const
, etc) from within an example group where those APIs are unavailable. (Myron Marston, #1819) - Add new
RSpec::Core::Sandbox.sandboxed { }
API that facilitates testing RSpec with RSpec, allowing you to define example groups and example from within an example without affecting the globalRSpec.world
state. (Tyler Ball, 1808) - Apply line-number filters only to the files they are scoped to, allowing you to mix filtered and unfiltered files. (Myron Marston, #1839)
- When dumping pending examples, include the failure details so that you don't have to un-pend the example to see it. (Myron Marston, #1844)
- Make
-I
option support multiple values when separated byFile::PATH_SEPARATOR
, such asrspec -I foo:bar
. This matches the behavior of Ruby's-I
option. (Fumiaki Matsushima, #1855).
Bug Fixes:
- When assigning generated example descriptions, surface errors
raised by
matcher.description
in the example description. (Myron Marston, #1771) - Don't consider expectations from
after
hooks when generating example descriptions. (Myron Marston, #1771) - Don't apply metadata-filtered config hooks to examples in groups with matching metadata when those examples override the parent metadata value to not match. (Myron Marston, #1796)
- Fix
config.expect_with :minitest
so thatskip
uses RSpec's implementation rather than Minitest's. (Jonathan Rochkind, #1822) - Fix
NameError
caused when duplicate example group aliases are defined and the DSL is not globally exposed. (Aaron Kromer, #1825) - When a shared example defined in an external file fails, use the host example group (from a loaded spec file) for the re-run command to ensure the command will actually work. (Myron Marston, #1835)
- Fix location filtering to work properly for examples defined in a nested example group within a shared example group defined in an external file. (Bradley Schaefer, Xavier Shay, Myron Marston, #1837)
- When a pending example fails (as expected) due to a mock expectation,
set
RSpec::Core::Example::ExecutionResult#pending_exception
-- previously it was not being set but should have been. (Myron Marston, #1844) - Fix rake task to work when
rspec-core
is installed in a directory containing a space. (Guido Günther, #1845) - Fix regression in 3.1 that caused
describe Regexp
to raise errors. (Durran Jordan, #1853)
3.1.8 Development
Bug Fixes:
- Apply
--seed
before loading--require
files so that required files can access the provided seed. (Myron Marston, #1745) - Handle
RSpec::Core::Formatters::DeprecationFormatter::FileStream
being reopened with an IO stream, which sometimes happens with spring. (Kevin Mook, #1757)
3.1.7 / 2014-10-11
Bug Fixes:
- Fix
Metadata.relative_path
so that for a current directory of/foo/bar
,/foo/bar_1
is not wrongly converted to._1
. (Akos Vandra, #1730) - Prevent constant lookup mistakenly finding
RSpec::ExampleGroups
generated constants on 1.9.2 by appending a trailing_
to the generated names. (Jon Rowe, #1737) - Fix bug in
:pending
metadata. If it got set in any way besides passing it as part of the metadata literal passed toit
(such as by usingdefine_derived_metadata
), it did not have the desired effect, instead marking the example as:passed
. (Myron Marston, #1739)
3.1.6 / 2014-10-08
Bug Fixes:
- Fix regression in rake task pattern handling, that prevented patterns
that were relative from the current directory rather than from
spec
from working properly. (Myron Marston, #1734) - Prevent rake task from generating duplicate load path entries. (Myron Marston, #1735)
3.1.5 / 2014-09-29
Bug Fixes:
- Fix issue with the rake task incorrectly escaping strings on Windows. (Jon Rowe #1718)
- Support absolute path patterns. While this wasn't officially supported
previously, setting
rake_task.pattern
to an absolute path pattern in RSpec 3.0 and before worked since it delegated toFileList
internally (but now just forwards the pattern on to therspec
command). (Myron Marston, #1726)
3.1.4 / 2014-09-18
Bug Fixes:
- Fix implicit
subject
when usingdescribe false
ordescribe nil
so that it returns the provided primitive rather than the string representation. (Myron Marston, #1710) - Fix backtrace filtering to allow code in subdirectories of your current working directory (such as vendor/bundle/...) to be filtered from backtraces. (Myron Marston, #1708)
3.1.3 / 2014-09-15
Bug Fixes:
- Fix yet another regression in rake task pattern handling, to allow
task.pattern = FileList["..."]
to work. That was never intended to be supported but accidentally worked in 3.0 and earlier. (Myron Marston, #1701) - Fix pattern handling so that files are normalized to absolute paths
before subtracting the
--exclude-pattern
matched files from the--pattern
matched files so that it still works even if the patterns are in slightly different forms (e.g. one starting with./
). (Christian Nelson, #1698)
3.1.2 / 2014-09-08
Bug Fixes:
- Fix another regression in rake task pattern handling, so that patterns
that start with
./
still work. (Christian Nelson, #1696)
3.1.1 / 2014-09-05
Bug Fixes:
- Fix a regression in rake task pattern handling, so that
rake_task.pattern = array
works again. While we never intended to support array values (or even knew that worked!), the implementation from 3.0 and earlier usedFileList
internally, which allows arrays. The fix restores the old behavior. (Myron Marston, #1694)
3.1.0 / 2014-09-04
Enhancements:
- Update files generated by
rspec --init
so that warnings are enabled in commented out section ofspec_helper
rather than.rspec
so users have to consciously opt-in to the setting. (Andrew Hooker, #1572) - Update
spec_helper
generated byrspec --init
so that it sets the new rspec-expectationsinclude_chain_clauses_in_custom_matcher_descriptions
config option (which will be on by default in RSpec 4) and also sets the rspec-mocksverify_partial_doubles
option (which will also default to on in RSpec 4). (Myron Marston, #1647) - Provide an
inspect
output for example procsy objects (used in around hooks) that doesn't make them look like procs. (Jon Rowe, #1620) - Remove a few unneeded
require
statements fromrspec/core/rake_task.rb
, making it even more lighterweight. (Myron Marston, #1640) - Allow rspec-core to be used when neither rspec-mocks or rspec-expectations are installed, without requiring any user configuration. (Sam Phippen, Myron Marston, #1615)
- Don't filter out gems from backtraces by default. (The RSpec gems will still be filtered). User feedback has indicated that including gems in default backtraces will be useful. (Myron Marston, #1641)
- Add new
config.filter_gems_from_backtrace "rack", "rake"
API to easily filter the named gems from backtraces. (Myron Marston, #1682) - Fix default backtrace filters so that the RSpec binary is
excluded when installing RSpec as a bundler
:git
dependency. (Myron Marston, #1648) - Simplify command generated by the rake task so that it no longer
includes unnecessary
-S
. (Myron Marston, #1559) - Add
--exclude-pattern
CLI option,config.exclude_pattern =
config option andtask.exclude_pattern =
rake task config option. Matching files will be excluded. (John Gesimondo, Myron Marston, #1651, #1671) - When an around hook fails to execute the example, mark it as pending (rather than passing) so the user is made aware of the fact that the example did not actually run. (Myron Marston, #1660)
- Remove dependency on
FileUtils
from the standard library so that users do not get false positives where their code relies on it but they are not requiring it. (Sam Phippen, #1565)
Bug Fixes:
- Fix rake task
t.pattern =
option so that it does not run all specs when it matches no files, by passing along a--pattern
option to therspec
command, rather than resolving the file list and passing along the files individually. (Evgeny Zislis, #1653) - Fix rake task default pattern so that it follows symlinks properly. (Myron Marston, #1672)
- Fix default pattern used with
rspec
command so that it follows symlinks properly. (Myron Marston, #1672) - Change how we assign constant names to example group classes so that
it avoids a problem with
describe "Core"
. (Daniela Wellisz, #1679) - Handle rendering exceptions that have a different encoding than that of their original source file. (Jon Rowe, #1681)
- Allow access to message_lines without colour for failed examples even when they're part of a shared example group. (tomykaira, #1689)
3.0.4 / 2014-08-14
Bug Fixes:
- Fix processing order of CLI options so that if
config.files_to_run
is accessed from a file loaded by--require
,--pattern
is still applied. (Myron Marston, #1652) - Fix
config.pattern=
so that it still takes affect even ifconfig.files_to_run
has already been accessed. (Myron Marston, #1652)
3.0.3 / 2014-07-21
Bug Fixes:
- Properly convert both parts of a description into strings before concatenation. (@nicklink483, #1636)
- Exclude the working directory when figuring out folders to ignore. (Jon Rowe, Myron Marston, #1616)
- Allow
::RSpec::Core::Notifications::FailedExampleNotification#message_lines
to be accessed without a colouriser. (@tomykaira, #1637)
3.0.2 / 2014-06-19
Bug Fixes:
- Fix regression in CLI option handling that prevented
--tag slow
passed at the command line from overriding--tag ~slow
in.rspec
. (Colin Jones, #1602) - Fix metadata
:example_group
deprecation warning so that it gets issued at the call site of the configuration that specified it as a filter rather than later when an example group is defined. (Myron Marston, #1562) - Make the line that is printed when a shared example group fails indicating where the concrete example group is white, separating it from the stack trace that is produced for the failure. (Sam Phippen, Jon Rowe, #1606)
3.0.1 / 2014-06-12
Bug Fixes:
- Fix a couple ruby warnings caused by rspec-core when loaded. (Prem Sichanugrist, #1584)
- Example groups named
Config
will no longer cause a Ruby warning to be issued. (Jimmy Cuadra, #1580)
3.0.0 / 2014-06-01
Bug Fixes:
- Fix
BaseTextFormatter
so that it does not re-close a closed output stream. (Myron Marston) - Fix regression in metadata that caused the metadata hash of a top-level
example group to have a
:parent_example_group
key even though it has no parent example group. (Myron Marston)
Enhancements:
- Alter the default
spec_helper.rb
to no longer recommendconfig.full_backtrace = true
see #1536 for discussion. (Jon Rowe)
3.0.0.rc1 / 2014-05-18
Breaking Changes for 3.0.0:
- Change
described_class
so that in a nested group likedescribe MyClass
, it returnsMyClass
rather than the outer group's described class. (Myron Marston) - Refactor filter manager so that it no longer subclasses Hash and has a tighter, more domain-specific interface. (Sergey Pchelincev)
- Remove legacy colours definitions from
BaseTextFormatter
. (Jon Rowe) - Remove console color definitions from
BaseTextFormatter
. (Jon Rowe) - Restructure example group metadata so that the computed keys are
exposed directly off of the metadata hash rather than being on
a nested
:example_group
subhash. In addition, the parent example group metadata is now available as[:parent_example_group]
rather than[:example_group][:example_group]
. Deprecated access via the old key structure is still provided. (Myron Marston) - Remove
:describes
metadata key. It duplicates:described_class
for no good reason. Deprecated access via:describes
is still provided. (Myron Marston) - Rename
:example_group_block
metadata key to:block
. (Myron Marston) - Remove deprecated
RSpec::Core::Example#options
. (Myron Marston) - Move
BaseTextFormatter#colorize_summary
toSummaryNotification#colorize_with
(Jon Rowe). describe some_hash
treatedsome_hash
as metadata in RSpec 2.x but will treat it as the described object in RSpec 3.0. Metadata must always come after the description args. (Myron Marston)- Remove deprecated
display_name
alias ofExampleGroup.description
. (Myron Marston) - Remove deprecated
describes
alias ofExampleGroup.described_class
. (Myron Marston) - Remove deprecated
RSpec::Core::ExampleGroup.alias_it_behaves_like_to
. UseRSpec::Core::Configuration#alias_it_behaves_like_to
instead. (Myron Marston) - Remove deprecated
RSpec::Core::ExampleGroup.alias_example_to
. UseRSpec::Core::Configuration#alias_example_to
instead. (Myron Marston) - Removed
focused
example alias and change example/group aliasesfit
,focus
,fcontext
andfdescribe
to no longer include:focused => true
metadata. They only contain:focus => true
metadata now. This means that you will need to filter them withfilter_run :focus
, notfilter_run :focused
. (Myron Marston) - Remove
--line-number
filtering. It's semantically dubious since it's a global filter (potentially applied to multiple files) but there's no meaningful connection between the same line number in multiple files. Instead use therspec path/to/spec.rb:23:46
form, which is terser and makes more sense as it is scoped to a file. (Myron Marston) - Remove
--default_path
as an alias for--default-path
. (Jon Rowe) - Remove deprecated
share_examples_for
. There's stillshared_examples
andshared_examples_for
. (Myron Marston) - Rename
RSpec::Core::Configuration#warnings
toRSpec::Core::Configuration#warnings?
since it's a boolean flag. (Myron Marston) - RSpec's global state is no longer reset after a spec run. This gives more flexibility to alternate runners to decide when and if they want the state reset. Alternate runners are now responsible for calling this (or doing a similar reset) if they are going to run the spec suite multiple times in the same process. (Sam Phippen)
- Merge
RSpec::Core::CommandLine
(never formally declared public) intoRSpec::Core::Runner
. (Myron Marston) - Remove
color_enabled
as an alias ofcolor
. (Jon Rowe) - Remove
backtrace_cleaner
as an alias ofbacktrace_formatter
. (Jon Rowe) - Remove
filename_pattern
as an alias ofpattern
. (Jon Rowe) - Extract support for legacy formatters to
rspec-legacy_formatters
. (Jon Rowe) RSpec::Configuration#formatters
now returns a dup to prevent mutation. (Jon Rowe)- Replace
stdlib
as an available expectation framework withtest_unit
andminitest
. (Aaron Kromer) - Remove backtrace formatting helpers from
BaseTextFormatter
. (Jon Rowe) - Extract profiler support to
ProfileFormatter
andProfileNotification
. Formatters should implementdump_profile
if they wish to respond to--profile
. (Jon Rowe) - Extract remaining formatter state to reporter and notifications. Introduce
ExamplesNotification
to share information about examples that was previously held inBaseFormatter
. (Jon Rowe)
Enhancements:
- Add
config.default_formatter
attribute, which can be used to set a formatter which will only be used if no other formatter is set (e.g. via--formatter
). (Myron Marston) - Support legacy colour definitions in
LegacyFormatterAdaptor
. (Jon Rowe) - Migrate
execution_result
(exposed by metadata) from a hash to a first-class object with appropriate attributes.status
is now stored and returned as a symbol rather than a string. It retains deprecated hash behavior for backwards compatibility. (Myron Marston) - Provide console code helper for formatters. (Jon Rowe)
- Use raw ruby hashes for the metadata hashes rather than a subclass of a hash. Computed metadata entries are now computed in advance rather than being done lazily on first access. (Myron Marston)
- Add
:block
metadata entry to the example metadata, bringing parity with:block
in the example group metadata. (Myron Marston) - Add
fspecify
andfexample
as aliases ofspecify
andexample
with:focus => true
metadata for parity withfit
. (Myron Marston) - Add legacy support for
colorize_summary
. (Jon Rowe) - Restructure runner so it can be more easily customized in a subclass for an alternate runner. (Ben Hoskings)
- Document
RSpec::Core::ConfigurationOptions
as an officially supported public API. (Myron Marston) - Add
--deprecation-out
CLI option which directs deprecation warnings to the named file. (Myron Marston) - Minitest 5 compatability for
expect_with :stdlib
(now available asexpect_with :minitest
). (Xavier Shay) - Reporter now notifies formatters of the load time of RSpec and your
specs via
StartNotification
andSummaryNotification
. (Jon Rowe) - Add
disable_monkey_patching!
config option that disables all monkey patching from whatever pieces of RSpec you use. (Alexey Fedorov) - Add
Pathname
support for setting all output streams. (Aaron Kromer) - Add
config.define_derived_metadata
, which can be used to apply additional metadata to all groups or examples that match a given filter. (Myron Marston) - Provide formatted and colorized backtraces via
FailedExampleNotification
and sendPendingExampleFixedNotifications
when the error is due to a passing spec you expect to fail. (Jon Rowe) - Add
dump_profile
to formatter API to allow formatters to implement support for--profile
. (Jon Rowe) - Allow colourising text via
ConsoleCodes
with RSpec 'states' (e.g.:success
,:failure
) rather than direct colour codes. (Jon Rowe) - Expose
fully_formatted
methods off the formatter notification objects that make it easy for a custom formatter to produce formatted output like rspec-core's. (Myron Marston)
Bug Fixes:
- Fix
spec_helper.rb
file generated byrspec --init
so that the recommended settings correctly use the documentation formatter when running one file. (Myron Marston) - Fix ordering problem where descriptions were generated after tearing down mocks, which resulted in unexpected exceptions. (Bradley Schaefer, Aaron Kromer, Andrey Savchenko)
- Allow a symbol to be used as an implicit subject (e.g.
describe :foo
). (Myron Marston) - Prevent creating an isolated context (i.e. using
RSpec.describe
) when already inside a context. There is no reason to do this, and it could potentially cause unexpected bugs. (Xavier Shay) - Fix shared example group scoping so that when two shared example groups share the same name at different levels of nested contexts, the one in the nearest context is used. (Myron Marston)
- Fix
--warnings
option so that it enables warnings immediately so that it applies to files loaded by--require
. (Myron Marston) - Issue a warning when you set
config.deprecation_stream
too late for it to take effect because the reporter has already been setup. (Myron Marston) - Add the full
RSpec::Core::Example
interface to the argument yielded toaround
hooks. (Myron Marston) - Line number always takes precendence when running specs with filters. (Xavier Shay)
- Ensure :if and :unless metadata filters are treated as a special case and are always in-effect. (Bradley Schaefer)
- Ensure the currently running installation of RSpec is used when
the rake task shells out to
rspec
, even if a newer version is also installed. (Postmodern) - Using a legacy formatter as default no longer causes an infinite loop. (Xavier Shay)
3.0.0.beta2 / 2014-02-17
Breaking Changes for 3.0.0:
- Make
mock_with
option more strict. Strings are no longer supported (e.g.mock_with "mocha"
) -- use a symbol instead. Also, unrecognized values will now result in an error rather than falling back to the null mocking adapter. If you want to use the null mocking adapter, usemock_with :nothing
(as has been documented for a long time). (Myron Marston) - Remove support for overriding RSpec's built-in
:if
and:unless
filters. (Ashish Dixit) - Custom formatters are now required to call
RSpec::Core::Formatters.register(formatter_class, *notifications)
wherenotifications
is the list of events the formatter wishes to be notified about. Notifications are handled by methods matching the names on formatters. This allows us to add or remove notifications without breaking existing formatters. (Jon Rowe) - Change arguments passed to formatters. Rather than passing multiple arguments (which limits are ability to add additional arguments as doing so would break existing formatters), we now pass a notification value object that exposes the same data via attributes. This will allow us to add new bits of data to a notification event without breaking existing formatters. (Jon Rowe)
- Remove support for deprecated
:alias
option forRSpec.configuration.add_setting
. (Myron Marston) - Remove support for deprecated
RSpec.configuration.requires = [...]
. (Myron Marston) - Remove support for deprecated
--formatter
CLI option. (Myron Marston) - Remove support for deprecated
--configure
CLI option. (Myron Marston) - Remove support for deprecated
RSpec::Core::RakeTask#spec_opts=
. (Myron Marston) - An example group level
pending
block or:pending
metadata now executes the example and cause a failure if it passes, otherwise it will be pending if it fails. The old "never run" behaviour is still used forxexample
,xit
, andxspecify
, or via a newskip
method or:skip
metadata option. (Xavier Shay) - After calling
pending
inside an example, the remainder of the example will now be run. If it passes a failure is raised, otherwise the example is marked pending. The old "never run" behaviour is provided a by a newskip
method. (Xavier Shay) - Pending blocks inside an example have been removed as a feature with no
direct replacement. Use
skip
orpending
without a block. (Xavier Shay) - Pending statement is no longer allowed in
before(:all)
hooks. Useskip
instead. (Xavier Shay) - Remove
show_failures_in_pending_blocks
configuration option. (Xavier Shay) - Remove support for specifying the documentation formatter using 's', 'n', 'spec' or 'nested'. (Jon Rowe)
Enhancements:
- Add example run time to JSON formatter output. (Karthik Kastury)
- Add more suggested settings to the files generated by
rspec --init
. (Myron Marston) - Add
config.alias_example_group_to
, which can be used to define a new method that defines an example group with the provided metadata. (Michi Huber) - Add
xdescribe
andxcontext
as shortcuts to skip an example group. (Myron Marston) - Add
fdescribe
andfcontext
as shortcuts to focus an example group. (Myron Marston) - Don't autorun specs via
#at_exit
by default.require 'rspec/autorun'
is only needed when running specs viaruby
, as it always has been. Running specs viarake
orrspec
are both unaffected. (Ben Hoskings) - Add
expose_dsl_globally
config option, defaulting to true. When disabled it will remove the monkey patches rspec-core adds tomain
andModule
(e.g.describe
,shared_examples_for
, etc). (Jon Rowe) - Expose RSpec DSL entry point methods (
describe
,shared_examples_for
, etc) on theRSpec
constant. Intended for use whenexpose_dsl_globally
is set tofalse
. (Jon Rowe) - For consistency, expose all example group aliases (including
context
) on theRSpec
constant. Ifexpose_dsl_globally
is set totrue
, also expose them onmain
andModule
. Historically, onlydescribe
was exposed. (Jon Rowe, Michi Huber) - Add hook scope
:example
as an alias for:each
, and:context
as an alias for:all
. (John Feminella)
Bug Fixes:
- Fix failure (undefined method
path
) in end-of-run summary whenraise_errors_for_deprecations!
is configured. (Myron Marston) - Issue error when attempting to use
-i
or--I
on command line, too close to-I
to be considered short hand for--init
. (Jon Rowe) - Prevent adding formatters to an output target if the same formatter has already been added to that output. (Alex Peattie)
- Allow a matcher-generated example description to be used when the example is pending. (Myron Marston)
- Ensure the configured
failure_exit_code
is used by the rake task when there is a failure. (Jon Rowe) - Restore behaviour whereby system exclusion filters take priority over working directory (was broken in beta1). (Jon Rowe)
- Prevent RSpec mangling file names that have substrings containing
line_number
ordefault_path
. (Matijs van Zuijlen) - Fix failure line detection so that it handles relative file paths
(which can happen when running specs through
ruby
usingrspec/autorun
). (Myron Marston, #1829)
3.0.0.beta1 / 2013-11-07
Breaking Changes for 3.0.0:
- Remove explicit support for 1.8.6. (Jon Rowe)
- Remove
RSpec::Core::ExampleGroup#example
andRSpec::Core::ExampleGroup#running_example
methods. If you need access to the example (e.g. to get its metadata), use a block arg instead. (David Chelimsky) - Remove
TextMateFormatter
, it has been moved torspec-tmbundle
. (Aaron Kromer) - Remove RCov integration. (Jon Rowe)
- Remove deprecated support for RSpec 1 constructs (Myron Marston):
- The
Spec
andRspec
constants (rather thanRSpec
). Spec::Runner.configure
rather thanRSpec.configure
.Rake::SpecTask
rather thanRSpec::Core::RakeTask
.
- The
- Remove deprecated support for
share_as
. (Myron Marston) - Remove
--debug
option (and corresponding option onRSpec::Core::Configuration
). Instead, use-r<debugger gem name>
to load whichever debugger gem you wish to use (e.g.ruby-debug
,debugger
, orpry
). (Myron Marston) - Extract Autotest support to a seperate gem. (Jon Rowe)
- Raise an error when a
let
orsubject
declaration is accessed in abefore(:all)
orafter(:all)
hook. (Myron Marston) - Extract
its
support to a separate gem. (Peter Alfvin) - Disallow use of a shared example group from sibling contexts, making them fully isolated. 2.14 and 2.99 allowed this but printed a deprecation warning. (Jon Rowe)
- Remove
RSpec::Core::Configuration#output
andRSpec::Core::Configuration#out
aliases ofRSpec::Core::Configuration#output_stream
. (Myron Marston) - Remove legacy ordering APIs deprecated in 2.99.0.beta1. (Myron Marston)
Enhancements:
- Replace unmaintained syntax gem with coderay gem. (Xavier Shay)
- Times in profile output are now bold instead of
failure_color
. (Matthew Boedicker) - Add
--no-fail-fast
command line option. (Gonzalo Rodríguez-Baltanás Díaz) - Runner now considers the local system ip address when running under Drb. (Adrian CB)
- JsonFormatter now includes
--profile
information. (Alex / @MasterLambaster) - Always treat symbols passed as metadata args as hash
keys with true values. RSpec 2 supported this with the
treat_symbols_as_metadata_keys_with_true_values
but now this behavior is always enabled. (Myron Marston) - Add
--dry-run
option, which prints the formatter output of your suite without running any examples or hooks. (Thomas Stratmann, Myron Marston) - Document the configuration options and default values in the
spec_helper.rb
file that is generated by RSpec. (Parker Selbert) - Give generated example group classes a friendly name derived from the docstring, rather than something like "Nested_2". (Myron Marston)
- Avoid affecting randomization of user code when shuffling examples so that users can count on their own seeds working. (Travis Herrick)
- Ordering is no longer a single global property of the test suite.
Each group can pick an ordering using
:order
metadata. (Andy Lindeman, Sam Phippen, Myron Marston) - Allow named custom ordering strategies to be registered, which can then be used on individual example groups. (Andy Lindeman, Sam Phippen, Myron Marston)
Deprecations:
treat_symbols_as_metadata_keys_with_true_values
is deprecated and no longer has an affect now that the behavior it enabled is always enabled. (Myron Marston)
2.99.2 / 2014-08-19
Enhancements:
- Improve deprecation warning for RSpec 3 change in
describe <a symbol>
behavior. (Jon Rowe, #1667)
2.99.1 / 2014-06-19
Bug Fixes:
- Add missing deprecation warning for when
RSpec::Core::Runner
is used multiple times in the same process. In 2.x RSpec's global state was automatically cleared between runs but in 3.0 you need to callRSpec.reset
manually in these situations. (Sam Phippen, #1587) - Prevent deprecation being accidentally issues when doubles used with
be_
matchers due to automatically generated descriptions. (Jon Rowe, #1573) - Load
rspec/core
when loadingrspec/core/rake_task
to ensure we can issue deprecations correctly. (Jon Rowe, #1612)
2.99.0 / 2014-06-01
Bug Fixes:
- Fix
BaseTextFormatter
so that it does not re-close a closed output stream. (Myron Marston) - Use
RSpec::Configuration#backtrace_exclusion_patterns
rather than the deprecatedRSpec::Configuration#backtrace_clean_patterns
when mocking with rr. (David Dollar)
2.99.0.rc1 / 2014-05-18
Enhancements:
- Add
--deprecation-out
CLI option which directs deprecation warnings to the named file. (Myron Marston) - Backport support for
skip
in metadata to skip execution of an example. (Xavier Shay, #1472) - Add
Pathname
support for setting all output streams. (Aaron Kromer) - Add
test_unit
andminitest
expectation frameworks. (Aaron Kromer)
Deprecations:
- Deprecate
RSpec::Core::Pending::PendingDeclaredInExample
, useSkipDeclaredInExample
instead. (Xavier Shay) - Issue a deprecation when
described_class
is accessed from within a nesteddescribe <SomeClass>
example group, sincedescribed_class
will return the innermost described class in RSpec 3 rather than the outermost described class, as it behaved in RSpec 2. (Myron Marston) - Deprecate
RSpec::Core::FilterManager::DEFAULT_EXCLUSIONS
,RSpec::Core::FilterManager::STANDALONE_FILTERS
and use of#empty_without_conditional_filters?
on those filters. (Sergey Pchelincev) - Deprecate
RSpec::Core::Example#options
in favor ofRSpec::Core::Example#metadata
. (Myron Marston) - Issue warning when passing a symbol or hash to
describe
orcontext
as the first argument. In RSpec 2.x this would be treated as metadata but in RSpec 3 it'll be treated as the described object. To continue having it treated as metadata, pass a description before the symbol or hash. (Myron Marston) - Deprecate
RSpec::Core::BaseTextFormatter::VT100_COLORS
andRSpec::Core::BaseTextFormatter::VT100_COLOR_CODES
in favour ofRSpec::Core::BaseTextFormatter::ConsoleCodes::VT100_CODES
andRSpec::Core::BaseTextFormatter::ConsoleCodes::VT100_CODE_VALUES
. (Jon Rowe) - Deprecate
RSpec::Core::ExampleGroup.display_name
in favor ofRSpec::Core::ExampleGroup.description
. (Myron Marston) - Deprecate
RSpec::Core::ExampleGroup.describes
in favor ofRSpec::Core::ExampleGroup.described_class
. (Myron Marston) - Deprecate
RSpec::Core::ExampleGroup.alias_example_to
in favor ofRSpec::Core::Configuration#alias_example_to
. (Myron Marston) - Deprecate
RSpec::Core::ExampleGroup.alias_it_behaves_like_to
in favor ofRSpec::Core::Configuration#alias_it_behaves_like_to
. (Myron Marston) - Deprecate
RSpec::Core::ExampleGroup.focused
in favor ofRSpec::Core::ExampleGroup.focus
. (Myron Marston) - Add deprecation warning for
config.filter_run :focused
since example aliasesfit
andfocus
will no longer include:focused
metadata but will continue to include:focus
. (Myron Marston) - Deprecate filtering by
:line_number
(e.g.--line-number
from the CLI). Use location filtering instead. (Myron Marston) - Deprecate
--default_path
as an alternative to--default-path
. (Jon Rowe) - Deprecate
RSpec::Core::Configuration#warnings
in favor ofRSpec::Core::Configuration#warnings?
. (Myron Marston) - Deprecate
share_examples_for
in favor ofshared_examples_for
or justshared_examples
. (Myron Marston) - Deprecate
RSpec::Core::CommandLine
in favor ofRSpec::Core::Runner
. (Myron Marston) - Deprecate
#color_enabled
,#color_enabled=
and#color?
in favour of#color
,#color=
and#color_enabled? output
. (Jon Rowe) - Deprecate
#filename_pattern
in favour of#pattern
. (Jon Rowe) - Deprecate
#backtrace_cleaner
in favour of#backtrace_formatter
. (Jon Rowe) - Deprecate mutating
RSpec::Configuration#formatters
. (Jon Rowe) - Deprecate
stdlib
as an available expectation framework in favour oftest_unit
andminitest
. (Aaron Kromer)
Bug Fixes:
- Issue a warning when you set
config.deprecation_stream
too late for it to take effect because the reporter has already been setup. (Myron Marston) skip
with a block should not execute the block. (Xavier Shay)
2.99.0.beta2 / 2014-02-17
Enhancements:
- Add
is_expected
for one-liners that read well with theexpect
-based syntax.is_expected
is simply defined asexpect(subject)
and can be used in an expression like:it { is_expected.to read_well }
. (Myron Marston) - Backport
skip
from RSpec 3, which acts likepending
did in RSpec 2 when not given a block, since the behavior ofpending
is changing in RSpec 3. (Xavier Shay)
Deprecations:
- Deprecate inexact
mock_with
config options. RSpec 3 will only support the exact symbols:rspec
,:mocha
,:flexmock
,:rr
or:nothing
(or any module that implements the adapter interface). RSpec 2 did fuzzy matching but this will not be supported going forward. (Myron Marston) - Deprecate
show_failures_in_pending_blocks
config option. To achieve the same behavior as the option enabled, you can use a custom formatter instead. (Xavier Shay) - Add a deprecation warning for the fact that the behavior of
pending
is changing in RSpec 3 -- rather than skipping the example (as it did in 2.x when no block was provided), it will run the example and mark it as failed if no exception is raised. Useskip
instead to preserve the old behavior. (Xavier Shay) - Deprecate 's', 'n', 'spec' and 'nested' as aliases for documentation formatter. (Jon Rowe)
- Deprecate
RSpec::Core::Reporter#abort
in favor ofRSpec::Core::Reporter#finish
. (Jon Rowe)
Bug Fixes:
- Fix failure (undefined method
path
) in end-of-run summary whenraise_errors_for_deprecations!
is configured. (Myron Marston) - Fix issue were overridding spec ordering from the command line wasn't fully recognised interally. (Jon Rowe)
2.99.0.beta1 / 2013-11-07
Enhancements
- Block-based DSL methods that run in the context of an example
(
it
,before(:each)
,after(:each)
,let
andsubject
) now yield the example as a block argument. (David Chelimsky) - Warn when the name of more than one example group is submitted to
include_examples
and it's aliases. (David Chelimsky) - Add
expose_current_running_example_as
config option for use during the upgrade process when external gems use the deprecatedRSpec::Core::ExampleGroup#example
andRSpec::Core::ExampleGroup#running_example
methods. (Myron Marston) - Limit spamminess of deprecation messages. (Bradley Schaefer, Loren Segal)
- Add
config.raise_errors_for_deprecations!
option, which turns deprecations warnings into errors to surface the full backtrace of the call site. (Myron Marston)
Deprecations
- Deprecate
RSpec::Core::ExampleGroup#example
andRSpec::Core::ExampleGroup#running_example
methods. If you need access to the example (e.g. to get its metadata), use a block argument instead. (David Chelimsky) - Deprecate use of
autotest/rspec2
in favour ofrspec-autotest
. (Jon Rowe) - Deprecate RSpec's built-in debugger support. Use a CLI option like
-rruby-debug
(for the ruby-debug gem) or-rdebugger
(for the debugger gem) instead. (Myron Marston) - Deprecate
RSpec.configuration.treat_symbols_as_metadata_keys_with_true_values = false
. RSpec 3 will not support having this option set tofalse
. (Myron Marston) - Deprecate accessing a
let
orsubject
declaration in aafter(:all)
hook. (Myron Marston, Jon Rowe) - Deprecate built-in
its
usage in favor ofrspec-its
gem due to planned removal in RSpec 3. (Peter Alfvin) - Deprecate
RSpec::Core::PendingExampleFixedError
in favor ofRSpec::Core::Pending::PendingExampleFixedError
. (Myron Marston) - Deprecate
RSpec::Core::Configuration#out
andRSpec::Core::Configuration#output
in favor ofRSpec::Core::Configuration#output_stream
. (Myron Marston) - Deprecate legacy ordering APIs.
- You should use
register_ordering(:global)
instead of these: RSpec::Core::Configuration#order_examples
RSpec::Core::Configuration#order_groups
RSpec::Core::Configuration#order_groups_and_examples
- These are deprecated with no replacement because in RSpec 3 ordering is a property of individual example groups rather than just a global property of the entire test suite:
RSpec::Core::Configuration#order
RSpec::Core::Configuration#randomize?
--order default
is deprecated in favor of--order defined
(Myron Marston)
- You should use
2.14.8 / 2014-02-27
Bug fixes:
- Fix regression with the
textmateformatter
that prevented backtrace links from being clickable. (Stefan Daschek)
2.14.7 / 2013-10-29
Bug fixes:
- Fix regression in 2.14.6 that broke the Fivemat formatter.
It depended upon either
example.execution_result[:exception].pending_fixed?
(which was removed in 2.14.6 to fix an issue with frozen error objects) orRSpec::Core::PendingExampleFixedError
(which was renamed toRSpec::Core::Pending::PendingExampleFixedError
in 2.8. This fix makes a constant alias for the old error name. (Myron Marston)
2.14.6 / 2013-10-15
Bug fixes:
- Format stringified numbers correctly when mathn library is loaded. (Jay Hayes)
- Fix an issue that prevented the use of frozen error objects. (Lars Gierth)
2.14.5 / 2013-08-13
Bug fixes:
- Fix a
NoMethodError
that was being raised when there were no shared examples or contexts declared andRSpec.world.reset
is invoked. (thepoho, Jon Rowe, Myron Marston) - Fix a deprecation warning that was being incorrectly displayed when
shared_examples
are declared at top level in amodule
scope. (Jon Rowe) - Fix after(:all) hooks so consecutive (same context) scopes will run even if one raises an error. (Jon Rowe, Trejkaz)
- JsonFormatter no longer dies if
dump_profile
isn't defined (Alex / @MasterLambaster, Jon Rowe)
2.14.4 / 2013-07-21
Bug fixes
- Fix regression in 2.14: ensure configured requires (via
-r
option) are loaded before spec files are loaded. This allows the spec files to programatically change the file pattern (Jon Rowe). - Autoload
RSpec::Mocks
andRSpec::Expectations
when referenced if they are not already loaded (RSpec::Matches
has been autoloaded for a while). In therspec
gem, we changed it recently to stop loadingrspec/mocks
andrspec/expectations
by default, as some users reported problems where they were intending to use mocha, not rspec-mocks, but rspec-mocks was loaded and causing a conflict. rspec-core loads mocks and expectations at the appropriate time, so it seemed like a safe change -- but caused a problem for some authors of libraries that integrate with RSpec. This fixes that problem. (Myron Marston) - Gracefully handle a command like
rspec --profile path/to/spec.rb
: thepath/to/spec.rb
arg was being wrongly treated as theprofile
integer arg, which got cast0
usingto_i
, causing no profiled examples to be printed. (Jon Rowe)
2.14.3 / 2013-07-13
Bug fixes
- Fix deprecation notices issued from
RSpec::Core::RakeTask
so that they work properly when all of rspec-core is not loaded. (This was a regression in 2.14) (Jon Rowe)
2.14.2 / 2013-07-09
Bug fixes
- Fix regression caused by 2.14.1 release: formatters that
report that they
respond_to?
a notification, but had no corresponding method would raise an error when registered. The new fix is to just implementstart
on the deprecation formatter to fix the original JRuby/ruby-debug issue. (Jon Rowe)
2.14.1 / 2013-07-08
Bug fixes
- Address deprecation formatter failure when using
ruby-debug
on JRuby: fixRSpec::Core::Reporter
to not send a notification when the formatter's implementation of the notification method comes fromKernel
(Alex Portnov, Jon Rowe).
2.14.0 / 2013-07-06
Enhancements
- Apply focus to examples defined with
fit
(equivalent ofit "description", focus: true
) (Michael de Silva)
Bug fix
- Ensure methods defined by
let
take precedence over others when there is a name collision (e.g. from an included module). (Jon Rowe, Andy Lindeman and Myron Marston)
2.14.0.rc1 / 2013-05-27
Enhancements
- Improved Windows detection inside Git Bash, for better
--color
handling. - Add profiling of the slowest example groups to
--profile
option. The output is sorted by the slowest average example groups. - Don't show slow examples if there's a failure and both
--fail-fast
and--profile
options are used (Paweł Gościcki). - Rather than always adding
spec
to the load path, add the configured--default-path
to the load path (which defaults tospec
). This better supports folks who choose to put their specs in a different directory (John Feminella). - Add some logic to test time duration precision. Make it a function of time, dropping precision as the time increases. (Aaron Kromer)
- Add new
backtrace_inclusion_patterns
config option. Backtrace lines that match one of these patterns will always be included in the backtrace, even if they match an exclusion pattern, too (Sam Phippen). - Support ERB trim mode using the
-
when parsing.rspec
as ERB (Gabor Garami). - Give a better error message when let and subject are called without a block. (Sam Phippen).
- List the precedence of
.rspec-local
in the configuration documentation (Sam Phippen) - Support
{a,b}
shell expansion syntax in--pattern
option (Konstantin Haase). - Add cucumber documentation for --require command line option (Bradley Schaefer)
- Expose configuration options via config:
config.libs
returns the libs configured to be added onto the load pathfull_backtrace?
returns the state of the backtrace cleanerdebug?
returns true when the debugger is loadedline_numbers
returns the line numbers we are filtering by (if any)full_description
returns the RegExp used to filter descriptions (Jon Rowe)
- Add setters for RSpec.world and RSpec.configuration (Alex Soulim)
- Configure ruby's warning behaviour with
--warnings
(Jon Rowe) - Fix an obscure issue on old versions of
1.8.7
whereTime.dup
wouldn't allow access toTime.now
(Jon Rowe) - Make
shared_examples_for
context aware, so that keys may be safely reused in multiple contexts without colliding. (Jon Rowe) - Add a configurable
deprecation_stream
(Jon Rowe) - Publish deprecations through a formatter (David Chelimsky)
Bug fixes
- Make JSON formatter behave the same when it comes to
--profile
as the text formatter (Paweł Gościcki). - Fix named subjects so that if an inner group defines a method that
overrides the named method,
subject
still retains the originally declared value (Myron Marston). - Fix random ordering so that it does not cause
rand
in examples in nested sibling contexts to return the same value (Max Shytikov). - Use the new
backtrace_inclusion_patterns
config option to ensure that folks who develop code in a directory matching one of the default exclusion patterns (e.g.gems
) still get the normal backtrace filtering (Sam Phippen). - Fix ordering of
before
hooks so thatbefore
hooks declared inRSpec.configure
run beforebefore
hooks declared in a shared context (Michi Huber and Tejas Dinkar). - Fix
Example#full_description
so that it gets filled in by the last matcher description (asExample#description
already did) when no doc string has been provided (David Chelimsky). - Fix the memoized methods (
let
andsubject
) leakingdefine_method
as apublic
method. (Thomas Holmes and Jon Rowe) (#873) - Fix warnings coming from the test suite. (Pete Higgins)
Deprecations
- Deprecate
Configuration#backtrace_clean_patterns
in favor ofConfiguration#backtrace_exclusion_patterns
for greater consistency and symmetry with newbacktrace_inclusion_patterns
config option (Sam Phippen). - Deprecate
Configuration#requires=
in favor of using ruby'srequire
. Requires specified by the command line can still be accessed by theConfiguration#require
reader. (Bradley Schaefer) - Deprecate calling
SharedExampleGroups
defined across sibling contexts (Jon Rowe)
2.13.1 / 2013-03-12
Bug fixes
- Use hook classes as proxies rather than extending hook blocks to support lambdas for before/after/around hooks. (David Chelimsky)
- Fix regression in 2.13.0 that caused confusing behavior when overriding
a named subject with an unnamed subject in an inner group and then
referencing the outer group subject's name. The fix for this required
us to disallow using
super
in a named subject (which is confusing, anyway -- named subjects create 2 methods, so which method on the parent example group are yousuper
ing to?) butsuper
in an unnamed subject continues to work (Myron Marston). - Do not allow a referenced
let
orsubject
inbefore(:all)
to cause otherlet
declarations to leak across examples (Myron Marston). - Work around odd ruby 1.9 bug with
String#match
that was triggered by passing it a regex from alet
declaration. For more info, see http://bugs.ruby-lang.org/issues/8059 (Aaron Kromer). - Add missing
require 'set'
tobase_text_formatter.rb
(Tom Anderson).
Deprecations
- Deprecate accessing
let
orsubject
declarations inbefore(:all)
. These were not intended to be called in abefore(:all)
hook, as they exist to define state that is reset between each example, whilebefore(:all)
exists to define state that is shared across examples in an example group (Myron Marston).
2.13.0 / 2013-02-23
Enhancements
- Allow
--profile
option to take a count argument that determines the number of slow examples to dump (Greggory Rothmeier). - Add
subject!
that is the analog tolet!
. It defines an explicit subject and sets abefore
hook that will invoke the subject (Zubin Henner). - Fix
let
andsubject
declaration so thatsuper
andreturn
can be used in them, just like in a normal method. (Myron Marston) - Allow output colors to be configured individually. (Charlie Maffitt)
- Always dump slow examples when
--profile
option is given, even when an example failed (Myron Marston).
Bug fixes
- Don't blow up when dumping error output for instances of anonymous error classes (Myron Marston).
- Fix default backtrace filters so lines from projects containing "gems" in the name are not filtered, but lines from installed gems still are (Myron Marston).
- Fix autotest command so that is uses double quotes rather than single quotes for windows compatibility (Jonas Tingeborn).
- Fix
its
so that uses ofsubject
in abefore
orlet
declaration in the parent group continue to reference the parent group's subject. (Olek Janiszewski)
2.12.2 / 2012-12-13
Bug fixes
- Fix
RSpec::Core::RakeTask
so that it is compatible with rake 0.8.7 on ruby 1.8.7. We had accidentally broke it in the 2.12 release (Myron Marston). - Fix
RSpec::Core::RakeTask
so it is tolerant of theRspec
constant for backwards compatibility (Patrick Van Stee)
2.12.1 / 2012-12-01
Bug fixes
- Specs are run even if another at_exit hook calls
exit
. This allows Test::Unit and RSpec to run together. (Suraj N. Kurapati) - Fix full doc string concatenation so that it handles the case of a method string (e.g. "#foo") being nested under a context string (e.g. "when it is tuesday"), so that we get "when it is tuesday #foo" rather than "when it is tuesday#foo". (Myron Marston)
- Restore public API I unintentionally broke in 2.12.0:
RSpec::Core::Formatters::BaseFormatter#format_backtrce(backtrace, example)
(Myron Marston).
2.12.0 / 2012-11-12
Enhancements
- Add support for custom ordering strategies for groups and examples. (Myron Marston)
- JSON Formatter (Alex Chaffee)
- Refactor rake task internals (Sam Phippen)
- Refactor HtmlFormatter (Pete Hodgson)
- Autotest supports a path to Ruby that contains spaces (dsisnero)
- Provide a helpful warning when a shared example group is redefined. (Mark Burns).
--default_path
can be specified as--default-line
.--line_number
can be specified as--line-number
. Hyphens are more idiomatic command line argument separators (Sam Phippen).- A more useful error message is shown when an invalid command line option is used (Jordi Polo).
- Add
format_docstrings { |str| }
config option. It can be used to apply formatting rules to example group and example docstrings. (Alex Tan) - Add support for an
.rspec-local
options file. This is intended to allow individual developers to set options in a git-ignored file that override the common project options in.rspec
. (Sam Phippen) - Support for mocha 0.13.0. (Andy Lindeman)
Bug fixes
- Remove override of
ExampleGroup#ancestors
. This is a core ruby method that RSpec shouldn't override. Instead, defineExampleGroup#parent_groups
. (Myron Marston) - Limit monkey patching of shared example/context declaration methods
(
shared_examples_for
, etc.) to just the objects that need it rather than every object in the system (Myron Marston). - Fix Metadata#fetch to support computed values (Sam Goldman).
- Named subject can now be referred to from within subject block in a nested group (tomykaira).
- Fix
fail_fast
so that it properly exits when an error occurs in abefore(:all) hook
(Bradley Schaefer). - Make the order spec files are loaded consistent, regardless of the order of the files returned by the OS or the order passed at the command line (Jo Liss and Sam Phippen).
- Ensure instance variables from
before(:all)
are always exposed fromafter(:all)
, even if an error occurs inbefore(:all)
(Sam Phippen). rspec --init
no longer generates an incorrect warning about--configure
being deprecated (Sam Phippen).- Fix pluralization of
1 seconds
(Odin Dutton) - Fix ANSICON url (Jarmo Pertman)
- Use dup of Time so reporting isn't clobbered by examples that modify Time without properly restoring it. (David Chelimsky)
Deprecations
share_as
is no longer needed.shared_context
and/orRSpec::SharedContext
provide better mechanisms (Sam Phippen).- Deprecate
RSpec.configuration
with a block (useRSpec.configure
).
2.11.1 / 2012-07-18
Bug fixes
- Fix the way we autoload RSpec::Matchers so that custom matchers can be defined before rspec-core has been configured to definitely use rspec-expectations. (Myron Marston)
- Fix typo in --help message printed for -e option. (Jo Liss)
- Fix ruby warnings. (Myron Marston)
- Ignore mock expectation failures when the example has already failed. Mock expectation failures have always been ignored in this situation, but due to my changes in 27059bf1 it was printing a confusing message. (Myron Marston).
2.11.0 / 2012-07-07
Enhancements
- Support multiple
--example
options. (Daniel Doubrovkine @dblock) - Named subject e.g.
subject(:article) { Article.new }
- see http://blog.davidchelimsky.net/2012/05/13/spec-smell-explicit-use-of-subject/ for background.
- thanks to Bradley Schaefer for suggesting it and Avdi Grimm for almost suggesting it.
config.mock_with
andconfig.expect_with
yield custom config object to a block if given- aids decoupling from rspec-core's configuation
include_context
andinclude_examples
support a block, which gets eval'd in the current context (vs the nested context generated byit_behaves_like
).- Add
config.order = 'random'
to thespec_helper.rb
generated byrspec --init
. - Delay the loading of DRb (Myron Marston).
- Limit monkey patching of
describe
onto just the objects that need it rather than every object in the system (Myron Marston).
Bug fixes
- Support alternative path separators. For example, on Windows, you can now do
this:
rspec spec\subdir
. (Jarmo Pertman @jarmo) - When an example raises an error and an after or around hook does as well, print out the hook error. Previously, the error was silenced and the user got no feedback about what happened. (Myron Marston)
--require
and-I
are merged among different configuration sources (Andy Lindeman)- Delegate to mocha methods instead of aliasing them in mocha adapter.
2.10.1 / 2012-05-19
Bug fixes
RSpec.reset
properly reinits configuration and world- Call
to_s
beforesplit
on exception messages that might not always be Strings (slyphon)
2.10.0 / 2012-05-03
Enhancements
- Add
prepend_before
andappend_after
hooks (preethiramdev)- intended for extension libs
- restores rspec-1 behavior
- Reporting of profiled examples (moro)
- Report the total amount of time taken for the top slowest examples.
- Report what percentage the slowest examples took from the total runtime.
Bug fixes
- Properly parse
SPEC_OPTS
options. example.description
returns the location of the example if there is no explicit description or matcher-generated description.- RDoc fixes (Grzegorz Świrski)
- Do not modify example ancestry when dumping errors (Michael Grosser)
2.9.0 / 2012-03-17
Enhancements
- Support for "X minutes X seconds" spec run duration in formatter. (uzzz)
- Strip whitespace from group and example names in doc formatter.
- Removed spork-0.9 shim. If you're using spork-0.8.x, you'll need to upgrade to 0.9.0.
Bug fixes
- Restore
--full_backtrace
option - Ensure that values passed to
config.filter_run
are respected when running over DRb (using spork). - Ensure shared example groups are reset after a run (as example groups are).
- Remove
rescue false
from calls to filters represented as Procs - Ensure
described_class
gets the closest constant (pyromaniac) - In "autorun", don't run the specs in the
at_exit
hook if there was an exception (most likely due to a SyntaxError). (sunaku) - Don't extend groups with modules already used to extend ancestor groups.
its
correctly memoizes nil or false values (Yamada Masaki)
2.8.0 / 2012-01-04
Bug fixes
- For metadata filtering, restore passing the entire array to the proc, rather than each item in the array (weidenfreak)
- Ensure each spec file is loaded only once
- Fixes a bug that caused all the examples in a file to be run when
referenced twice with line numbers in a command, e.g.
rspec path/to/file:37 path/to/file:42
- Fixes a bug that caused all the examples in a file to be run when
referenced twice with line numbers in a command, e.g.
2.8.0.rc2 / 2011-12-19
Enhancments
- new
--init
command (Peter Schröder)- generates
spec/spec_helper.rb
- deletes obsolete files (on confirmation)
- merged with and deprecates
--configure
command, which generated.rspec
- generates
- use
require_relative
when available (Ian Leitch) include_context
andinclude_examples
accept params (Calvin Bascom)- print the time for every example in the html formatter (Richie Vos)
- several tasty refactoring niblets (Sasha)
- `it "does something", :x => :foo,'bar',/baz/
- supports matching n command line tag values with an example or group
2.8.0.rc1 / 2011-11-06
Enhancements
--order
(Justin Ko)- run examples in random order:
--order rand
- specify the seed:
--order rand:123
- run examples in random order:
--seed SEED
- equivalent of
--order rand:SEED
- equivalent of
- SharedContext supports
let
(David Chelimsky) - Filter improvements (David Chelimsky)
- override opposing tags from the command line
- override RSpec.configure tags from the command line
--line_number 37
overrides all other filterspath/to/file.rb:37
overrides all other filters- refactor: consolidate filter management in a FilterManger object
- Eliminate Ruby warnings (Matijs van Zuijlen)
- Make reporter.report an API (David Chelimsky)
- supports extension tools like interative_rspec
Changes
- change
config.color_enabled
(getter/setter/predicate) tocolor
to align with--[no]-color
CLI option.color_enabled
is still supported for now, but will likley be deprecated in a 2.x release so we can remove it in 3.0.
Bug fixes
- Make sure the
bar
in--tag foo:bar
makes it to DRb (Aaron Gibralter) - Fix bug where full descriptions of groups nested 3 deep were repeated.
- Restore report of time to run to start after files are loaded.
- fixes bug where run times were cumalitive in spork
- fixes compatibility with time-series metrics
Don't error out when
config.mock_with
orexpect_with
is re-specifying the current config (Myron Marston)Deprecations
- :alias option on
configuration.add_setting
. Use:alias_with
on the original setting declaration instead.
- :alias option on
2.7.1 / 2011-10-20
Bug fixes
- tell autotest the correct place to find the rspec executable
2.7.0 / 2011-10-16
NOTE: RSpec's release policy dictates that there should not be any backward incompatible changes in minor releases, but we're making an exception to release a change to how RSpec interacts with other command line tools.
As of 2.7.0, you must explicity require "rspec/autorun"
unless you use the
rspec
command (which already does this for you).
Enhancements
- Add
example.exception
(David Chelimsky) --default_path
command line option (Justin Ko)- support multiple
--line_number
options (David J. Hamilton)- also supports
path/to/file.rb:5:9
(runs examples on lines 5 and 9)
- also supports
- Allow classes/modules to be used as shared example group identifiers (Arthur Gunn)
- Friendly error message when shared context cannot be found (Sławosz Sławiński)
- Clear formatters when resetting config (John Bintz)
- Add
xspecify
and xexample as temp-pending methods (David Chelimsky) - Add
--no-drb
option (Iain Hecker) - Provide more accurate run time by registering start time before code is
loaded (David Chelimsky)
- reverted in 2.8.0
- Rake task default pattern finds specs in symlinked dirs (Kelly Felkins)
- Rake task no longer does anything to invoke bundler since Bundler already handles it for us. Thanks to Andre Arko for the tip.
- Add
--failure-exit-code
option (Chris Griego)
Bug fixes
- Include
Rake::DSL
to remove deprecation warnings in Rake > 0.8.7 (Pivotal Casebook) - Only eval
let
block once even if it returnsnil
(Adam Meehan) - Fix
--pattern
option (wasn't being recognized) (David Chelimsky) - Only implicitly
require "rspec/autorun"
with therspec
command (David Chelimsky) - Ensure that rspec's
at_exit
defines the exit code (Daniel Doubrovkine) - Show the correct snippet in the HTML and TextMate formatters (Brian Faherty)
2.6.4 / 2011-06-06
NOTE: RSpec's release policy dictates that there should not be new functionality in patch releases, but this minor enhancement slipped in by accident. As it doesn't add a new API, we decided to leave it in rather than roll back this release.
Enhancements
- Add summary of commands to run individual failed examples.
Bug fixes
- Support exclusion filters in DRb. (Yann Lugrin)
- Fix --example escaping when run over DRb. (Elliot Winkler)
- Use standard ANSI codes for color formatting so colors work in a wider set of color schemes.
2.6.3 / 2011-05-24
Bug fixes
- Explicitly convert exit code to integer, avoiding TypeError when return
value of run is IO object proxied by
DRb::DRbObject
(Julian Scheid) - Clarify behavior of
--example
command line option - Build using a rubygems-1.6.2 to avoid downstream yaml parsing error
2.6.2 / 2011-05-21
Bug fixes
- Warn rather than raise when HOME env var is not defined
- Properly merge command-line exclusions with default :if and :unless (joshcooper)
2.6.1 / 2011-05-19
Bug fixes
- Don't extend nil when filters are nil
require 'rspec/autorun'
when running rcov.
2.6.0 / 2011-05-12
Enhancements
shared_context
(Damian Nurzynski)- extend groups matching specific metadata with:
- method definitions
- subject declarations
- let/let! declarations
- etc (anything you can do in a group)
- extend groups matching specific metadata with:
its([:key])
works for any subject with #[]. (Peter Jaros)treat_symbols_as_metadata_keys_with_true_values
(Myron Marston)- Print a deprecation warning when you configure RSpec after defining an example. All configuration should happen before any examples are defined. (Myron Marston)
- Pass the exit status of a DRb run to the invoking process. This causes specs run via DRb to not just return true or false. (Ilkka Laukkanen)
- Refactoring of
ConfigurationOptions#parse_options
(Rodrigo Rosenfeld Rosas) - Report excluded filters in runner output (tip from andyl)
- Clean up messages for filters/tags.
- Restore --pattern/-P command line option from rspec-1
- Support false as well as true in config.full_backtrace= (Andreas Tolf Tolfsen)
Bug fixes
- Don't stumble over an exception without a message (Hans Hasselberg)
- Remove non-ascii characters from comments that were choking rcov (Geoffrey Byers)
- Fixed backtrace so it doesn't include lines from before the autorun at_exit hook (Myron Marston)
- Include RSpec::Matchers when first example group is defined, rather than just before running the examples. This works around an obscure bug in ruby 1.9 that can cause infinite recursion. (Myron Marston)
- Don't send
example_group_[started|finished]
to formatters for empty groups. - Get specs passing on jruby (Sidu Ponnappa)
- Fix bug where mixing nested groups and outer-level examples gave unpredictable :line_number behavior (Artur Małecki)
- Regexp.escape the argument to --example (tip from Elliot Winkler)
- Correctly pass/fail pending block with message expectations
- CommandLine returns exit status (0/1) instead of true/false
- Create path to formatter output file if it doesn't exist (marekj).
2.5.1 / 2011-02-06
NOTE: this release breaks compatibility with rspec/autotest/bundler integration, but does so in order to greatly simplify it.
With this release, if you want the generated autotest command to include 'bundle exec', require Autotest's bundler plugin in a .autotest file in the project's root directory or in your home directory:
require "autotest/bundler"
Now you can just type 'autotest' on the commmand line and it will work as you expect.
If you don't want 'bundle exec', there is nothing you have to do.
2.5.0 / 2011-02-05
Enhancements
- Autotest::Rspec2 parses command line args passed to autotest after '--'
- --skip-bundler option for autotest command
- Autotest regexp fixes (Jon Rowe)
- Add filters to html and textmate formatters (Daniel Quimper)
- Explicit passing of block (need for JRuby 1.6) (John Firebaugh)
Bug fixes
- fix dom IDs in HTML formatter (Brian Faherty)
- fix bug with --drb + formatters when not running in drb
- include --tag options in drb args (monocle)
- fix regression so now SPEC_OPTS take precedence over CLI options again (Roman Chernyatchik)
- only call its(:attribute) once (failing example from Brian Dunn)
- fix bizarre bug where rspec would hang after String.alias :to_int :to_i (Damian Nurzynski)
Deprecations
- implicit inclusion of 'bundle exec' when Gemfile present (use autotest's bundler plugin instead)
2.4.0 / 2011-01-02
Enhancements
- start the debugger on -d so the stack trace is visible when it stops (Clifford Heath)
- apply hook filtering to examples as well as groups (Myron Marston)
- support multiple formatters, each with their own output
- show exception classes in failure messages unless they come from RSpec matchers or message expectations
- before(:all) { pending } sets all examples to pending
Bug fixes
- fix bug due to change in behavior of reject in Ruby 1.9.3-dev (Shota Fukumori)
- fix bug when running in jruby: be explicit about passing block to super (John Firebaugh)
- rake task doesn't choke on paths with quotes (Janmejay Singh)
- restore --options option from rspec-1
- require 'ostruct' to fix bug with its([key]) (Kim Burgestrand)
- --configure option generates .rspec file instead of autotest/discover.rb
2.3.1 / 2010-12-16
Bug fixes
- send debugger warning message to $stdout if RSpec.configuration.error_stream has not been defined yet.
- HTML Formatter finally properly displays nested groups (Jarmo Pertman)
- eliminate some warnings when running RSpec's own suite (Jarmo Pertman)
2.3.0 / 2010-12-12
Enhancements
- tell autotest to use "rspec2" if it sees a .rspec file in the project's root
directory
- replaces the need for ./autotest/discover.rb, which will not work with all versions of ZenTest and/or autotest
- config.expect_with
- :rspec # => rspec/expectations
- :stdlib # => test/unit/assertions
- :rspec, :stdlib # => both
Bug fixes
- fix dev Gemfile to work on non-mac-os machines (Lake Denman)
- ensure explicit subject is only eval'd once (Laszlo Bacsi)
2.2.1 / 2010-11-28
Bug fixes * alias_method instead of override Kernel#method_missing (John Wilger) * changed --autotest to --tty in generated command (MIKAMI Yoshiyuki) * revert change to debugger (had introduced conflict with Rails) * also restored --debugger/-debug option
2.2.0 / 2010-11-28
Deprecations/changes
- --debug/-d on command line is deprecated and now has no effect
- win32console is now ignored; Windows users must use ANSICON for color support (Bosko Ivanisevic)
Enhancements
- When developing locally rspec-core now works with the rspec-dev setup or your local gems
- Raise exception with helpful message when rspec-1 is loaded alongside rspec-2 (Justin Ko)
- debugger statements just work as long as ruby-debug is installed
- otherwise you get warned, but not fired
- Expose example.metadata in around hooks
- Performance improvments (much faster now)
Bug fixes
- Make sure --fail-fast makes it across drb
- Pass -Ilib:spec to rcov
2.1.0 / 2010-11-07
Enhancments
- Add skip_bundler option to rake task to tell rake task to ignore the presence of a Gemfile (jfelchner)
- Add gemfile option to rake task to tell rake task what Gemfile to look for (defaults to 'Gemfile')
- Allow passing caller trace into Metadata to support extensions (Glenn Vanderburg)
- Add deprecation warning for Spec::Runner.configure to aid upgrade from RSpec-1
- Add deprecated Spec::Rake::SpecTask to aid upgrade from RSpec-1
- Add 'autospec' command with helpful message to aid upgrade from RSpec-1
- Add support for filtering with tags on CLI (Lailson Bandeira)
- Add a helpful message about RUBYOPT when require fails in bin/rspec (slyphon)
- Add "-Ilib" to the default rcov options (Tianyi Cui)
- Make the expectation framework configurable (default rspec, of course) (Justin Ko)
- Add 'pending' to be conditional (Myron Marston)
- Add explicit support for :if and :unless as metadata keys for conditional run of examples (Myron Marston)
- Add --fail-fast command line option (Jeff Kreeftmeijer)
Bug fixes
- Eliminate stack overflow with "subject { self }"
- Require 'rspec/core' in the Raketask (ensures it required when running rcov)
2.0.1 / 2010-10-18
Bug fixes
- Restore color when using spork + autotest
- Pending examples without docstrings render the correct message (Josep M. Bach)
- Fixed bug where a failure in a spec file ending in anything but _spec.rb would fail in a confusing way.
- Support backtrace lines from erb templates in html formatter (Alex Crichton)
2.0.0 / 2010-10-10
RSpec-1 compatibility
- Rake task uses ENV["SPEC"] as file list if present
Bug fixes
- Bug Fix: optparse --out foo.txt (Leonardo Bessa)
- Suppress color codes for non-tty output (except autotest)
2.0.0.rc / 2010-10-05
Enhancements
- implicitly require unknown formatters so you don't have to require the file explicitly on the commmand line (Michael Grosser)
- add --out/-o option to assign output target
- added fail_fast configuration option to abort on first failure
- support a Hash subject (its([:key]) { should == value }) (Josep M. Bach)
Bug fixes
- Explicitly require rspec version to fix broken rdoc task (Hans de Graaff)
- Ignore backtrace lines that come from other languages, like Java or Javascript (Charles Lowell)
- Rake task now does what is expected when setting (or not setting) fail_on_error and verbose
- Fix bug in which before/after(:all) hooks were running on excluded nested groups (Myron Marston)
- Fix before(:all) error handling so that it fails examples in nested groups, too (Myron Marston)
2.0.0.beta.22 / 2010-09-12
Enhancements
- removed at_exit hook
- CTRL-C stops the run (almost) immediately
- first it cleans things up by running the appropriate after(:all) and after(:suite) hooks
- then it reports on any examples that have already run
- cleaned up rake task
- generate correct task under variety of conditions
- options are more consistent
- deprecated redundant options
- run 'bundle exec autotest' when Gemfile is present
- support ERB in .rspec options files (Justin Ko)
- depend on bundler for development tasks (Myron Marston)
- add example_group_finished to formatters and reporter (Roman Chernyatchik)
Bug fixes
- support paths with spaces when using autotest (Andreas Neuhaus)
- fix module_exec with ruby 1.8.6 (Myron Marston)
- remove context method from top-level
- was conflicting with irb, for example
- errors in before(:all) are now reported correctly (Chad Humphries)
Removals
- removed -o --options-file command line option
- use ./.rspec and ~/.rspec


[§636C-2] Definition. In this chapter "foreign judgment" means any judgment, decree, or order of a court of the United States or of any other court which is entitled to full faith and credit in this State. [L 1983, c 31, pt of §1]


Join our network of grassroots organizations
The benefits of becoming a Givology partner are multifold. As a partner of Givology, you gain access to a new source of funding for your operations, a larger network to spread awareness about your cause, and a resource for social impact monitoring and volunteer recruitment. Given our network of donors and our presence on social media, your organization can benefit from our platform through numerous marketing and fundraising activities. Unlike listings on other crowd funding websites, we provide support to our partners on a highly personalized level - to work together to achieve your objectives. If you have any questions about the partnerships process, please contact<EMAIL_ADDRESS>for further details.
501-(c)3 status (or equivalent) or official institutions of education (i.e. local schools or universities) - Non-profit organizations based in the United States should have tax exemption status. NGOs abroad should have official non-profit status as recognized by local law. Official institutions of education should have documentation proving legitimacy of operations.
3+ years of field experience - we partner with organizations that have a proven track record, innovative model for impact, and deep relationships and commitments to their local community. Our partners are continually present in the communities they serve and are intimately familiar with the families and students they help.
Innovative impact model and targeting the right demographic - we look for partners that have a focused methodology for assessing impact. Potential partners should critically assess that that they are reaching truly needy students, rather than students who are more convenient or easier to serve.
Ability to provide regular updates - given our focus on transparency, we require our partners to provide regular updates about the progress of projects and scholarships that we list on Givology. Progress updates often come in the form of videos, staff descriptions, photos, letters from students, academic transcripts, or any other medium. As we post these updates on our website and social media channels, our partners benefit from increased donor interest and potential further funding!
Furthermore, 100% of the funding that we raise go to our partners - no fee from Givology in any transaction or transfer. We do this because as volunteers, we're passionate about making a difference


| EU GDP - Year on Year % | Actuals | |||||
| Release Dt | For period | Market Expectation | Kshitij Expectation | Previous | Released | Revised |
| 30-Jan-18 | Q4'17 First | - | 2.50 | 2.71 | 2.65 | - |
| 14-Feb-18 | Q4'17 Second | - | 2.86 | 2.65 | 2.68 | - |
| 7-Mar-18 | Q4'17 Final | - | 2.91 | 2.68 | 2.67 | - |
| 16-May-18 | Q1'18 First | - | 3.00 | 2.67 | - | - |
| Copyright: Kshitij Consultancy Services |


Girl's Day Out 2020
Home
Apply
Photo Gallery
Contact Us
FAQs
Photo Gallery
2019
2018
2017
2016
2015
×
❮
❯
×
❮
❯


Kindly submit the survey below and get to know which programming Language you should start with
Here is your survey outcome...
Dear ,
you should start with:
you should start with:
you should start with:
How can you get experience in programming without the knowedgle of coding
you should try something in which you have intrest


Independent
Web Developer
Hi! I'm a mid-lvl web developer from Belarus.
I develop websites, web applications and chatbots.
Here you can see my projects.
My Skills
HTML
CSS
JS
Feed


resolve¶
utility to pick overloaded C++ function calls
template <typename... Args, typename F>
constexpr auto resolve( F f );
resolve
is a function that is meant to help users pick a single function out of a group of overloaded functions in C++. It works for both member and free functions You can use it to pick overloads by specifying the signature as the first template argument. Given a collection of overloaded functions:
1 2 3 4 5 6 7 8 9 10 | int overloaded(int x);
int overloaded(int x, int y);
int overloaded(int x, int y, int z);
struct thing {
int overloaded() const;
int overloaded(int x);
int overloaded(int x, int y);
int overloaded(int x, int y, int z);
};
|
You can disambiguate them using resolve
:
1 2 3 4 5 | auto one_argument_func = resolve<int(int)>( overloaded );
auto two_argument_func = resolve<int(int, int)>( overloaded );
auto three_argument_func = resolve<int(int, int, int)>( overloaded );
auto member_three_argument_func = resolve<int(int, int, int)>( &thing::overloaded );
auto member_zero_argument_const_func = resolve<int() const>( &thing::overloaded );
|
It is important to note that const
is placed at the end for when you desire const overloads. You will get compiler errors if you are not specific and do not properly disambiguate for const member functions. This resolution also becomes useful when setting functions on a table or state_view:
1 2 3 4 5 | sol::state lua;
lua.set_function("a", resolve<int(int)>( overloaded ) );
lua.set_function("b", resolve<int(int, int)>( overloaded ));
lua.set_function("c", resolve<int(int, int, int)>( overloaded ));
|
It can also be used with sol::c_call:
1 2 3 4 5 6 7 8 9 | sol::state lua;
auto f = sol::c_call<
decltype(sol::resolve<int(int, int)>(&overloaded)),
sol::resolve<int(int, int)>(&overloaded)
>;
lua.set_function("f", f);
lua.script("f(1, 2)");
|