bekkopen / jasmineio Goto Github PK

Hi,
I would like to make a PR with changed directory structure that would work with Eerie package manager. Would you merge that PR?

Add a public landing page (github pages) for the project. We should probably use annotated source code to generate the page, similarly to what Jasmine does (and many other projects).

http://jashkenas.github.com/docco/ is the tool used to generate annotated source code pages. Docco uses Pygments for syntax highlighting, and pygments do support Io.

Is this meant to be open source software? Should we use it under the terms of the MIT/X11 License (same as Jasmine for JavaScript) or those of the Revised BSD License (same as Io itself)? Please add a license file to let prospective users know what legal restrictions may apply.

Should be possible to add a beforeEach and afterEach block to each suite. This will be an interesting feature, as we now need to think more carefully about scoping and which context each specification is execute in.

Add color to the runner (green for passing specs, red for failing specs).

Make it possible to execute the tests in "compact" mode, where you do not print every suite/spesification, but instead print a "O" if the test passes, and an "X" if it fails.

Jasmine supports nesting suites, and follow the scoping rules of JavaScript (an inner suite can access variables from an outer suite).

This would also be an interesting feature to add, as we would need to dig deeper into scoping/passing correct scope when executing a spec.

I checked out the master branch and launched io jasmine.io in the root directory, obtaining the following error:

Exception: argument 0 to method 'doMessage' must be a Message, not a 'nil'

doMessage jasmine.io 246
Suite run [unlabeled] 0
List mapInPlace [unlabeled] 0
List map jasmine.io 322
Call relayStopStatus A4_Exception.io 24
Call delegateToMethod A0_List.io 176
CLI doFile Z_CLI.io 140
CLI run IoState_runCLI() 1

I'm using Io installed from deb package on Ubuntu 12.04 64 bit.

$ io --version
Io Programming Language, v. 20110905

Currently we only have toBe, toEqual and toBeNil. We should probably add more matchers such as:

• toHaveSlot to check if a object has a given slot
• toContain to check if a List/Map contains an object
• toBeTrue and toBeFalse to check boolean expressions
• toThrow to check or exceptions

Adding the toThrow will greatly simplify our own testing of matchers, so it would make sense to implement this one first.