Table of contents:

1. 🌋 One mock server to rule them all
2. 🪲 Bug fixes
3. 🤑 Bulk payments [wip]
4. 📝 Communication card updates
5. 🐢 BFF ongoing work for the new profile menu

We went into this sprint a hobbit short, with Sebastian having to tend to other ventures for a few full moons and with Oskar the Wise only being able to guide us during half of his time. Two days ago we our third member Gustav departed on his journey on the Ålandic seas for the rest of the week. But fear not, they will be back.

Okay. So what have we been up to?

🌋 Aligning our mock server(s)

We in the Web Team have a thing that we like to call “The Mockserver” that we use when developing features locally and also when we are writing automatic tests for features. In short what this server does is basically imitating Kivra Core. This means that all of the endpoints that we on the web platform are using have been implemented in “The Mockserver”, but with mocked data instead of real or sandbox data. So when we’re setting up automatic tests, we’re changing the URL that we usually call (which points to Kivra Core) to instead point to “The Mockserver”.

In our tests we can do all sorts of things like adding contents, creating company users and basically everything that we need to make testing environment as realistic as possible.

Life was fine and dandy. But then the BFF happened (no worries, we love you BFF 💚).

Now we’re getting data from two sources: Kivra Core and the BFF. This means that now we need to mock the BFF for our automatic testing. So “The Mockserver (2)” was born. This little thing imitated the BFF so that we could use it for the same reasons as the old “The Mockserver”. But this means that we now have two mock servers that you need to spin up locally, and some of the data needs to be shared between the two which adds complexity. So… it is not that pleasant, really.

But!

We have started an initiative to combine these into one. This will bring us speed in the future when developing, will be much more pleasant in terms of DX and less complex than the alternative of having two. And to be transparent, it is not an easy feat to combine these. But we are soon there. Very soon.

(We hope)

🪲 Bug fixes

• Fixed a bug in settings where we sent the wrong data when a user opts out of getting reminders for unread content.

🤑 Bulk payments (work in progress)

This project started last sprint and it is now looking really promising. We have come quite far with this, although we still have quite a way to go. Since the concept of selecting and paying multiple invoices at the same time is new in the inbox, we want to take time to make proper decisions code wise that hopefully will make it easier to extend the payment part of web in the future as well.

📝 Communication card updates

We added two new communication cards into the mix that will hopefully drive more users towards K4B. One is shown for a small portion of private users and tries to convert those who have yet to create a business mailbox for their businesses. The other is shown for a group of current company users that are still to be converted to Kivra Business+.

Hopefully this is helpful for the K4B team.

🐢 Getting inbox groups from BFF

As we mentioned last week we were working on adding the possibility to get inbox groups from BFF. This is in preparation of the new profile menu that Team Discovery will work on later in T3. So, a short update on this is that the query is finally done. It combines four different APIs to create the data model that will be needed to display inbox groups in the updated profile menu. This is truly where the BFF shines, since we now have all that logic in one place (the BFF) instead of a separate implementation for every platform (Web, Android and iOS).

This query will be released next week. But many more will follow in the upcoming sprints.