The following is a working document and the information inside it will be updated regularly during the month of November 2026
NearBeach | Whelk | |
Current Bugs | 35 | 3 |
Code Coverage Frontend | 94.59% | 98.41% |
Code Coverage Backend | 89% | - |
The vast majority of unit tests have been completed for both NearBeach and Whelk-Ui. The next step is to review these tests and find any gaps we are missing, and to make sure we can scale out these tests when we deploy the other modules of NearBeach.
We have wrapped up most development for the verticle slice of 0.32, and now have started doing quality assurance and bug fixes. This includes;
Accessibility testing
A focus on User Experience
Flow of how functionalities work
As of writing, we have fixed all critical and show stopping bugs. Our goal is to fix all bugs before we start implementing other modules within NearBeach.
Click here for a list of all NearBeach issues
Whelk-Ui will also be going through it's own quality assurance and bug fixing cycle in NearBeach, as we expand how many components will be available on it.
One of our last goals in November is the update of our documentation. We are hoping to create documentation aimed at other developers, to help them understand NearBeach's structure and any other useful commands, i.e. running local tests and coverage reports.
We will also be reviewing the user facing documentation and applying more polish. We would love to hear some feedback.
This is reliant on how many issues we find in NearBeach, and if any large developments have to occur. However we are hoping to achieve the following;
Implementation of the public links front-end and API calls
Implementation of the organisation front-end and API calls
Implementation of the customer front-end and API calls
Implementation of the tasks module
Each of these developments with come with extra; front-end development, API development, quality assurance, unit testing, and end-to-end testing.