Working Document
This is a working document. We are currently keeping this updated during the month of November. Any crossed out items have been completed.
Information Updated On: April 26, 2024
Current: 6
Scheduled: 0
Release: 0
Blocked: 0
Code Coverage Backend: 70%
Code Coverage Frontend: 30%
0.31.15 on 26th of April, 2024
The great news is - we were able to do a full site test in November and ended up crushing 50 bugs. We want to do this again.
We have started to notice a lot of the bugs are no longer complicated, and are easy fixes (usually needing 1 - 5 lines of code). We are hoping this means NearBeach is getting to a rather stable point. Having this stable point means better feature implementations in the near future.
One area of improvement that did appear when both using NearBeach and testing, was the flow of an object.
The flow of an object is it's lifecycle from when a user creates the object, to when they finally close it. What happens if a user accidentally closes an object and needs to reopening it? Who can do that task, and how can they do that task? That is all part of the flow.
A lot of this flow adjustment will be just discussion for December. However we are hoping to improve it with small little fixes over the next coming months.
I am at that point where I need to sit down with someone who does not know anything about NearBeach and hand them the documentation. The idea of this is to gauge how well the documentation informs the users on how;
From this we can adjust our documentation or fill in the blanks where required. Documentation is a living document and will constantly be improved on each month.
We spent a lot of time in November getting the boiler plate unit tests up and running for the frontend of NearBeach. Along the way we were able to fix a couple of other issues that we noticed.
From here we are ready to start writing the unit tests for NearBeach's front end. This includes mocking up any axios calls, making sure the units render correctly etc.
We are hoping to achieve at least a 2% point increase for both the frontend and backend unit tests.
We sadly have let a few features slide in the last few months due to focusing on the NearBeach application. We are hoping to revisit the marketing site to make many improvements.
These improvements will hopefully allow us to create better blogs, and information pages. You can see some of the scheduled improvements in the above image.
Some of the new features we want to focus on are;
This is a community request.
Essentially we want to implement the ability for a read only link to be sent out so external users can follow up on their tasks/projects/cards/etc. We'll have to implement a way to control these links, i.e. delete them when no longer needed.
We have been using vitest for a while now. It is time to move the compiling of the code from Webpack into Vite.
This feature came about when I was confused at who can approve an RFC. There was no simple list telling me which users had the permission to approve said RFC.
If you would like to see our retrospective for November, you can visit our Patreon here - https://www.patreon.com/posts/november-2023-93609854