#Release

After the Phase 1, Run 1 testing there are quite a number of things that need fixing before we can move forward to a run-2 test phase. The work to do falls into these categories:

Features

There are three phase-1 features that escaped implementation. These are:

• FEAT-0225 - Archive scene
• FEAT-0226 - Unarchive scene
• FEAT-0227 - Delete scene

These missing features were responsible for many of the test failures that required the archiving, restoration or deletion of a scene as part of the test protocol. As the functionality was missing the tests failed.

Version v0.3.0 marked the final feature version for phase 1. So what’s next?

Testing it what’s next. Every requirement has a set of tests written using Gherkin syntax. This is a plain text description of the tests that can be automated to run as part of a continuos integration suite. However, there’s a lot of work involved in setting up the steps required for the automation, and so a decision was made to execute the test scripts manually.

The recently completed review and rework of the feature specification has allow me to make an accurate assessment of where there development of phase 1 is.

There are 35 features slated for the phase 1. Of these there are:

• 20 already fully implemented
• 10 that are partially implemented and need further work before release 1.0.0
• 5 that are not started yet.

Those last 5 are all related to the feature that implements novel parts as a structural layer above chapters. As parts are not used that often in novels (or the ones I read anyway) I had intended to postpone parts until a later phase. However, while reworking the features, I realized how disruptive it would be to implement it later. So it’s going into phase 1.

Novel-It is now publicly available on GitHub. The project is in active pre-v1.0 development and licensed under AGPL-3.0.