Integrated tests... are they really important?

Antonio Marcos Oliveira — Fri, 28 Jun 2024 13:32:11 +0000

On the last few weeks, I faced myself with a task to make integration tests for the database with our API, and a few questions came across my mind:

But aren't we already making unit tests?
All the effort will pay itself at the end?

So, along all the development path, I learned that even though we have to be open mind and ready to collaborate with your QA (if you have on your team), that also even if you have set up somenthing, meanwhile you are implementing the scenarios, you'll face new situations that require specifics setups and once you get over it, the development stops to be so stressful and starts to be fun and challeging. Free your imagination to think about the most exquisite situations (we know that funny things can happeng between two applications) and use this to reflect about if your unit tests suits are really being valuable or if it's just there to pass on sonarQube quality gates.

And yes, after finishing the implementation, I found some bugs that aren't visible even tough the API were exaustly tested, some of them critical which show me the importance the align the unit test it's not something to be left aside when you are planning the next steps of your project, not thinking that's luxury or somenthing secondary, but a crucial part of your application. Long short story, the application it's now more secure, maintainable and reliable for the users, ensuring less bugs, less headache for your team and more money wasted with your application off when can be simply evitable.

Git remote? What is that?

Antonio Marcos Oliveira — Tue, 18 Aug 2020 02:23:51 +0000

Hi guys! This is my first one article (and I hope that this could be the first one of a series) about my dev trajectory.
Well, today I want to share with you something that I passed through and even after some time using git, I've never stopped to think about it: git remote.
Due to this quarantine time, I've got more free time and decided to put into practice an old desire: learning React. So, I followed the tutorial (which is very helpful for who wants to start) and didn't follow the good practices by doing all the tutorials without making anyone commit.
So here begins the start of my saga: I create the repository on GitHub and follow all steps to push my code, but in a moment of distraction did a mistyping and add a ~ in the end of the link and try to push... and get an error. Tried again, and got the same error. Omg, what I could've done to get this error? Search on the web and nothing seems to be the solution to my error. Fortunately, I talked to a friend and she told me: well, you can show me the git remote of this repo? Even without understanding very well, search the command to do this
$ git remote -v and finally could see: a simple hookie mistake, but get me so frustrated, almost giving up on pushing the code. So, after seeing the mistake, hit another command to fix the connection to the real repo: $ git remote set-url origin git@hostname:USERNAME/REPOSITORY.git and could push my code to GitHub.
Well, I hope that my mistake could help some new devs who are starting to learn about code versioning. So, maybe I come back here to share new stories. See ya!

DEV Community: Antonio Marcos Oliveira

Integrated tests... are they really important?

Git remote? What is that?