Implement continuous integration about dart HOT 9 CLOSED

Dart currently uses a package called test that is the most popular framework for testing.

It comes with a configuration file called dart_test.yaml. Which would allow us customization over the testing process. I don't know if it will allow us control over the order of tests, though.

from dart.

I don't know if it will allow us control over the order of tests, though.

Yeah, most testing packages I've seen won't let you (and for good reason, mostly it's a terrible idea). It looks like the package lets you skip tests (https://github.com/dart-lang/test#skipping-tests) so this seems like a great choice.

from dart.

@kytrinyx and @SuperPaintman I haven't done anything with the Travis config file. Do either of you think it is ready? If not, what's missing?

from dart.

Right now it doesn't look like Travis is running the exercise test suites against their reference solutions. I think that's pretty key.

I've written up some thoughts about CI here: https://github.com/exercism/docs/blob/master/language-tracks/launch/tooling-and-ci.md

from dart.

Okay, so we want travis to run the example.dart files (reference solution) for each exercise... how do we do that without changing the file in the test suite that's referenced?

from dart.

@Stargator did you read the doc I linked to? The suggestion there is to write a script that copies everything to a tmp directory, and then changing the test suite so that it doesn't have skips, and renaming the reference solution so that it's whatever the test suite is expecting.

from dart.

Okay, I'll create an issue for that. But I don't think it should be labelled "good-first-patch" And I'll state it's due to the complex nature of copying a directory and making changes to a file.

from dart.

Agreed—that would not make a good first patch.

from dart.

Closing this as #34 will address the last steps for CI.

from dart.