When developing any app or system it’s crucial that our team constantly test the different versions to ensure they run smoothly and bug free.
This testing of functionalities and fixing of bugs is what we call QA: ‘Quality Assurance’.
We know that this all sounds terribly exciting, so we’ll give you a second to catch your breath and absorb that morsel of information.
QA can sometimes be a complicated and messy process and developers need to be organized in the way they discover and correct bugs. That is why using systems that organize such tasks is extremely helpful. This way developers can keep track of:
- Any new bugs that arise,
- Bugs ready for re-test; and
- Bugs that have been fixed.
The developers were using Bitbucket to manage all their source coding needs. Recently they have made the switch over to GitLab and they just swear by it. We realize that reviews of systems, much like social media, are essentially subjective. So although we do not consider ourselves the authority on this subject, here is a little on why GitLab has been working for us.
GitLab and Bitbucket are very similar in their functionalities; they both help the developers manage their source code. What essentially won over our team was the inclusive nature of GitLab. The whole VII Tech team is able to use it.
Often when undergoing QA, it will not just be the developers who sift through the app and test for bugs. Almost everyone at the office whether a designer, marketing officer or HR officer will have a go at testing the functionalities of the new app.
In order for a system to be used by developers and non developers, it has to be very user friendly.
This is why our team felt that GitLab had the upper hand. If someone finds a bug, GitLab has an organized space where team members can easily post the bug and rate its criticalness. Once the developers fix the bug, they just move it to the space designated for re-testing. In this way the whole team know which features to test to ensure that all bugs have been rectified.
Another reason why GitLab works better for us is the pricing strategy. Based on our subscription, we have an unlimited amount of users who can join in on all the QA’ing fun. Moreover for a monthly cost of $35, we get cloud hosting, maintenance, regular updates. Although Bitbucket was cheaper in comparison, it had a limitation on the number of users.
With GitLab, developers have a system where they can store source codes, have a company-wide knowledge base, integrate with third parties all without being inhibited by any QA work that needs to be shared between different teams. GitLab essentially works as a one-stop-shop for us and it’s amazing!
Learn more about GitLab here.