Venus 3.0

[sethmcl]

Venus 3.0

Venus 3.0 will be a major update to the framework. There are several areas of focus which I have in mind for this release.

Areas of focus

1. Plugin ecosystem. While Venus is customizable today, through custom test harness templates and reporters, there is much more we can do. I envision a plugin system, similar to what grunt provides.
2. Simplified configuration. Venus 2.0 supports nested configuration directories (.venus) in order to support the needs of large and diverse codebases. I believe the current configuration parsing logic adds unneeded complexity, and can be simplified to support a single .venus configuration directory, per project. We can solve the needs of large code bases in other ways.
3. Test result aggregation and CI integration. Supported by the new plugin model, we have the opportunity to better integrate with cloud providers (such as Sauce Labs), and CI systems such as Jenkins and Travis CI.
4. New user experience. Improve the experience of new users of the project, through an interactive venus init process.
5. Better support module loaders. Need to improve experience of using Venus with AMD and Common JS loaders, such as require.js and browserify.

Non-goals

1. Backwards compatibility. While I believe in preserving backwards compatibility if possible, the scope of the proposed changes may make this very difficult.