rudylattae / jasmine-species Goto Github PK

Provide a simple example -- calulator? -- that shows how jasmine-species may be applied in a non-trivial way to a BDD project.

There are a bunch of specs that are failing in Internet Explorer 8 on Win 7. I have not checked other versions of IE.

Environment:

• Windows 7
• Internet Explorer 8

It looks like the styling has not been updated to work with the latest version of jasmine.

Hy Rudy,

Since the GWT notation is commonly used as a partial documentation in agile software, I believe that supporting localization for the reports is a great feature. So I used Ely Grey's l10n library to add localization support for jasmine-species. If you feel this is a good contribution feel free to take a look in my fork at https://github.com/ericchaves/jasmine-species

I haven't made a pull request because I'm not really of a JS developer and therefore I'm not sure if my code is the best approach to it.

Best regards,

Eric.

The error is "target is null or not an object". Looks like this problem does not exist in the v1.0.1 release of jasmine's TrivialReporter.

Fix may be just a simple upgrade.

Environment:

• Windows 7
• Internet Explorer 8

• Revert usage of head.js
• Simplify the example as much as possible
• Extract description into the actual documentation page?

In order to start writing features and stories without additional dependencies
As a new jasmine-species user
I want to use a global setting to inject grammar into my global namespace

I am not a real fan of any js library dumping its innards or public api into my global namespace unless I ask for it. However since jasmine does this as a matter of convenience, jasmine-species, particularly the grammar package, should provide this "feature" to users.

It should help make it easier for new users to get up and running faster.

Proposed:

var jasmineSpecies_conf = {
    autoexport: [
        'jasmine.grammar.FeatureStory.*'
    ]
};

Ensure that the StyledHtmlReporter implementation reflects the latest updates to the jasmine.TrivialReporter

I guess as it don't support 1.2 then you already know this, but i thought i would register my interest.

If someone gave me some pointers i may fork and fix myself

Allen reported an issue he was having trying to use spies in Feature -> Scenario - >Given, ... setup. See: http://groups.google.com/group/jasmine-js/browse_thread/thread/22cede08b0932872

This issue will act as a progress tracker while I attempt to find a resolution.

1. Clearly indicate requirements for jasmine-species

Since the grammar is not auto-exported into the user's global namespace, they should be made aware of the fact that they need a javascript namespace importer of sorts (e.g. Namespace.js) to make the grammar available.

2. Reorganize the sections to improve allow users to move around easier

• Consider consolidating some sections
• Provide better context around the quick start example

While porting a jQuery plugin to CoffeeScript, I discovered your jasmine extensions and, more importantly, that the GWT grammar uses three CoffeeScript reserved words (when, then, and and) as function names.

At the time, I just rewrote my spec to avoid jasmine-species, but now I've forked your project and added three new, and hopefully comparable, functions to the grammar: whilst, hence, and likewise.

I've updated the specs to match, and will submit a pull request shortly, noting the number in a comment on this issue.

Once I've updated the docs, I'll submit a pull request for that, as well.

Using the namespaces might cause issues with code-completion tools. It does with Visual Studio.
In VS I can get IntelliSense to do the code-completion when I work in a seperate .js file. The trick is to use the following command:
/// < reference path="path-to-file.js" />
Unfortunatelly this doesn't work when the grammars are imported using Namespace.js. To make it work, I end up importing the names by hand, i.e.:

var given = jasmine.grammar.GWT.given;
var when = jasmine.grammar.GWT.when;
// etc.

This would be fine if it was enough, but currently I need to import some implementation specific stuff:

var _addStepToCurrentSpec = jasmine.grammar.GWT._addStepToCurrentSpec;

I'd like Jasmine Species to:

• drop the namespaces, or
• maintain manual import file, or
• let the user make the manual import, but make sure that he doesn't have to import implementation specific functions