DEV Community: Cinthia Barbosa da Silva

My Goals for 2026 in Technology

Cinthia Barbosa da Silva — Tue, 13 Jan 2026 21:06:05 +0000

Hi everybody,

I want to share some of my technology goals for 2026. Over the past years, I’ve learned a lot by practicing, working on real projects, and sharing knowledge with the community.
So, I want to share some of my technology goals for 2026 and what I’m planning to focus on this year!!

1) Post more content here on Dev Community

I don’t know if you know this, but I started writing here to share the technologies that I was learning and also to practice my English writing. I want to continue doing this and post more frequently, because sharing knowledge helps me learn better and improve my communication skills.

2) Document my backend experiences

In 2025, I was focused on backend development. I posted a personal project on GitHub using the knowledge I gained at work. Now, I want to go a step further and share these experiences here with documentation, challenges, and lessons learned along the way.

3) Study more about front-end

I started a new position, and now I work as a full-stack developer. That means I need to improve my front-end skills as well. I’m excited to learn new tools, frameworks, and best practices, and to become more confident building complete applications.

4) Study architecture and microservices

Another important goal is to study software architecture and microservices more deeply. I want to better understand the context, trade-offs, and real-world applications of these concepts, especially in scalable systems.

So...these goals are not just about learning new technologies, but also about growing as a developer and sharing this journey with the community. I hope that I can help others who are on a similar path!

Happy New Year to all! See you in the next post!

How to Analyze GitHub Projects with SonarQube Cloud

Cinthia Barbosa da Silva — Fri, 20 Jun 2025 22:32:38 +0000

Hi everybody,

In this article, I’ll show you how to perform code analysis on GitHub using SonarQube Cloud.

I’ve recently started using this tool at work, and I also use it in my personal projects on GitHub. If you’re not familiar with SonarQube Cloud, don’t worry, I’ll give you a quick overview of what it is and how you can easily set it up in your own project.

SonarQube Cloud created in 2017 is a tool for static code analysis that helps developers find and fix problems like:

Bugs
Vulnerabilities
Code Smells
Test Coverage
Security and Compliance Risks

SonarQube Cloud also works well with platforms like GitHub, GitLab, Bitbucket and Azure DevOps.

Now that you know a little bit about SonarQube Cloud, let’s get started with how to set up in your project!

The first step is to connect your GitHub account to SonarQube Cloud.

In my case, I already have some projects there, but I’ll share a link that shows how to connect your account and set everything up you need,
right here Get started with SonarCloud in 3 easy steps!

To start a new project, click the “+” icon at the top and choose “Analyze new project”.

I already have some projects in my account, but to create a new one, we need to click on "GitHub App Configuration."

After that, you’ll need to authenticate with your GitHub account. Then, you will be redirected to the "Installed GitHub Apps" page. There, click on "Configure" next to SonarCloud to proceed.

Here, "Repository Access," you have two options:

Only select repositories (the one I chose), or
All repositories (if you prefer, you can pick what works best for you.
).

I selected my repository "Products-api" and then clicked "Save"

Back in SonarQube Cloud, your new repository is now available. Just select it and click on "Set Up".

Next, you’ll see two setup options:

Previous version (this is the one I chose)
Number of days (you can choose this if it makes more sense for your project)

After selecting the option that your needs, click on "Create Project".

Now, back in the "products-api" repository on GitHub, we can see that SonarQube Cloud is connected and ready.

To trigger the first code analysis, we just need to make a commit in the project.

After making a commit to the main branch (or any other branch... SonarQube Cloud will analyze any branch as long as you push a new commit), the code analysis is automatically triggered.

Once the analysis is complete, you’ll see a summary of the results directly in the GitHub interface, under the “Checks” tab of your pull request or commit.

This summary includes useful information such as:

Whether the code passed or failed the Quality Gate
The number of bugs, vulnerabilities, and code smells found
The test coverage percentage
Any duplicated code

Here we can see some issues that were detected in my project by SonarQube Cloud, including this one and many other details.

That is for today. If you found this article helpful, please share and leave a comment.❤️

How to test authentication JWT on Thunder Client

Cinthia Barbosa da Silva — Fri, 27 Sep 2024 22:53:20 +0000

I am developing an API, and recently I needed to test an authentication endpoint using the Bearer Token method. It made me think... why not share this process with the Dev Community using Thunder Client? I have already written an article about what Thunder Client is and how to use this VS Code extension, which you can find here.

Let’s see how you can easily test authentication with Thunder Client! 🚀

Credentials: Normally in APIs, authentication starts with a POST request using credentials like an email and password. In my case, I’m using an email and password in the request body, to send to the API endpoint “api/v1/Authentication”

My GitHub with this repository: repository-github

Receive the response: After sending the request, the API responds with important details such as an access token, its expiry date, and possibly user data. The most important here is the token.

Use the token for authentication: With the token in hand, you can make further requests to protected endpoints by passing the token in the request header. In this example, we’re working with Bearer Token Authentication. In my case, I will use the endpoint “api/v1/GetAllProducts” to test getting products

Add token in Thunder Client: Click on the Auth tab in Thunder Client, select "Bearer Token" from the options, and paste your token in the field, then click on "Send"

Now, we can see the response with the authorization

If the Bearer token is not passed, the return will be Unauthorized as in the example below.

That is for today, If you found this article helpful, please share and leave a comment.❤️

Automating unit tests with xUnit on GitHub Actions

Cinthia Barbosa da Silva — Fri, 20 Sep 2024 23:56:19 +0000

Hi there!

In this article, I will share how you can run your unit tests using GitHub Actions!

Let's go!🚀

Before we start, make sure you have the following two basic steps:

A GitHub repository with your project.
Unit tests already implemented.

Now, let's implement CI on GitHub Actions. Here’s what you need to do:

In your repository, create two folders with the names .github/workflows.
Inside this folder workflows, create a file with the extension .yml, for example: run-tests.yml.

Next, it's time to define the steps to run your CI pipeline. Below is an example of how to set up your GitHub Actions workflow to run your unit tests.

name: CI - Unit Test

on:
  push:
    branches:
      - main
  pull_request:
    branches:
      - main

jobs:
  build:
    runs-on: ubuntu-latest

    steps:
      - name: Check out repository code
        uses: actions/checkout@v2

      - name: Set up .NET
        uses: actions/setup-dotnet@v3
        with:
          dotnet-version: '8.x'

      - name: Restore dependencies
        run: dotnet restore ./src/sales-management-api.sln

      - name: Build the solution
        run: dotnet build ./src/sales-management-api.sln --configuration Release --no-restore

      - name: Run unit tests with report
        run: dotnet test ./src/Test/Test.csproj --configuration Release --no-build --logger "trx;LogFileName=TestResults.trx"

      - name: Upload test results
        uses: actions/upload-artifact@v4
        with:
          name: TestResults
          path: ./src/Test/TestResults/TestResults.trx

Explaining the steps:

Check out repository code: This step clones your GitHub repository so that the actions can run on the source code.
Set up .NET: This configures the .NET SDK version you'll use to build and run tests, in my case, I am using version 8.
Restore dependencies: This restores all the necessary NuGet packages required by your project.
Build the solution: This compiles the code with the command dotnet build + path
Run unit tests: Runs the unit tests and generates a .trx report file with the command dotnet test + path
(Optional) Upload test results: This step uploads the test results as an artifact, allowing you to download and view the test output.

By following this setup, you’ll have continuous integration running your unit tests automatically when you push to the main branch or submit a pull request.

Now, every push will trigger the tests, and the results will be available in the Actions tab on GitHub.

We can see the result in “Run unit tests with report” how many tests passed or failed, as well as their duration.

My repository with this implementation: my-github

This is for today! If you have any questions, leave me a comment!

If you found this article helpful, please like the post.❤️

Essential Git Commands

Cinthia Barbosa da Silva — Sun, 14 Jul 2024 18:52:44 +0000

In this post we will learn the basic and essential commands of Git that developers use in their daily lives!

Let's go!🚀

Settings:

To set the global username

git config --global user.name "username"

To set the global email:

git config --global user.email "user@email.com"

Basic Commands:

To initialize a git repository

git init

To clone a repository

git clone <URL>

To check the changes

git status

To add a file

git add my-file

To add all changed files

git add .

To commit your changes

git commit -m "my first commit"

To push changes to the current branch

git push

To update your branch with changes

git pull

To switch branches

git checkout develop

To update your local repository with remove changes

git fetch

To create a new branch

git branch my-new-branch

Essential Command to Merge and check log:

To merge a branch

git merge my-branch

To check log

git log

To revert a commit

git revert 001

This is for today! If you have any questions, leave me a comment!

And you found this article helpful, please like the post.❤️

How to Publish Cypress Test Results to Azure Devops

Cinthia Barbosa da Silva — Sat, 15 Jun 2024 12:26:40 +0000

Continuing on the integration between Cypress and Azure Devops, in this post I am going to share how to publish test results!
If you found this article helpful, please leave a comment.❤️

Let's go!🚀

First of all, make sure your tests are in a Git repository (“Repos”) in Azure DevOps.

Next, we have to install the package JUnit Reporter for Cypress as a project dependency

$ npm install cypress-junit-reporter --save-dev

After that, in your Cypress test code, you need to configure the settings in the "cypress.config.js" file as follows:

reporter: 'mocha-junit-reporter',
  reporterOptions: {
    mochaFile: 'results/test-results-[hash].xml',
  }

Then, we need to include in the file .gitignore the folder "results", because every execution generates a new file with a hash code.

Now, navigate to Pipelines. If you already have a configured pipeline, locate it and click on Edit to make changes.

In your pipeline editor within Azure DevOps, navigate to Tasks and use the search bar to find the task named "Publish Test Results".

Now, you'll configure the task:

Set the "Test result format" to JUnit.
Set the path to publish the test files.
Check the option to merge test results.

After configuring these settings, click on Add to add the task to your pipeline.

Now, the configuration has been added to the azure-pipeline.yml file.

Once you have saved the azure-pipeline.yml file, initiate the test build by clicking on "Run Pipeline" in Azure DevOps. This action will start the CI/CD pipeline and execute the defined tasks, including a new configuration for test publish results.

After running the test, navigate to the "Test" to see a summary about the test, including execution time, how many tests passed and how many failed.

A very useful feature is that when a test fails we can create a "bug" task with all the details in Azure Devops!

This is for today! If you have any questions, leave me a comment!

And you found this article helpful, please like the post.❤️

Thunder Client: How to use to test APIs

Cinthia Barbosa da Silva — Sat, 04 May 2024 18:20:08 +0000

Recently, I started using an amazing VSCode extension called "Thunder Client" which makes it easy to make HTTP requests for testing APIs. I'm loving this tool! In this article, I will share what Thunder Client is how you can install it, and start using it today!

Let's go!🚀

What is Thunder Client?

Thunder Client is an extension for Visual Studio Code that simplifies API and web service testing. With it, you can make HTTP requests using GET, POST, PUT, DELETE, PATCH, HEAD, and OPTIONS methods. This extension aims to provide a simple, fast, and clean usability for the user.

How to install

The installation is simple, just search for the name "Thunder Client" in the "Extensions" of Vscode and click on install

By clicking "New request" we can see all the available HTTP methods (GET, POST, PUT, DELETE, PATCH, HEAD...) for making requests.

In just a few minutes, we can test it out. Here, I made a call to test an API that I had created. Basically, you input the URL, method, headers, or body if necessary on the left side, and on the right side, we receive the response.

We can create a collection and save our tests by clicking on the three dots and selecting the "Save to Collection" option.

Simply enter a request name, URL, select the Create New option and enter the new name. After that, save the changes.

Finally, we can see our saved collection on the left side under the "Collections" section.

If you found this article helpful, please leave a comment.❤️

Integration Cypress with Azure DevOps: Publishing test videos in your Pipeline

Cinthia Barbosa da Silva — Sun, 14 Apr 2024 15:16:31 +0000

Cypress is a front end test automation tool used for regression testing web applications. It is based in JavaScript and integrates seamlessly with many continuous integration tools, making it a great choice for automating tests.

I've been studying Cypress for a while now, especially it is integration with Azure DevOps. In this post, I will share how to publish videos from Cypress tests on Azure DevOps.

Let's go!🚀

First of all, make sure your tests are in a Git repository (“Repos”) in Azure DevOps.

Next, in your Cypress test code, you need to configure the settings in the "cypress.config.js" file as follows:

// cypress.config.js

module.exports = {
  video: true,
  videosFolder: 'cypress/videos'
};

Now, navigate to Pipelines. If you already have a configured pipeline, locate it and click on Edit to make changes.

After that, in your pipeline editor within Azure DevOps, navigate to Tasks and use the search bar to find the task named "publish build artifacts".

Now, you'll configure the task:

Set the Path to publish to specify where the artifact files will be stored in Azure.
Specify the Artifact name to give a name to your artifact.
Leave the Artifact publish location as default, normally set to "Azure Pipelines".

After configuring these settings, click on Add to add the task to your pipeline.

Now the configuration has been added to the azure-pipeline.yml file.

After running the test, navigate to the "Summary" and look for the information indicating "1 published artifact" and click on it.

This artifact contains the test recording.

By following these steps, you will use video recordings for better test analysis and debugging when necessary!

If you found this article helpful, please leave a comment.❤️

Deploy Angular website to GitHub Pages

Cinthia Barbosa da Silva — Fri, 29 Mar 2024 18:04:09 +0000

GitHub Pages is an excellent platform for deploying your websites and portfolios. I created my personal website using Angular and deployed it to GitHub Pages. During the process, I noticed that there are specific settings for this framework.

In this post, I will show you that in just a few steps, your project will be running!

Let's go!🚀

Create your GitHub Repository
First of all, you need to have an account in GitHub then, click on the “+” icon and select “New repository”

It is important to create a public repository and choose a name for it.

After creating the repository, commit all your changes and push your project files to the repository you created.

Now, in your project terminal, execute the command below to start the deployment process.

ng add angular-cli-ghpages

Navigate to your project directory and open the angular.json file. Add the "baseHref" with the name of your branch and then save the changes.

Now, execute the command "ng deploy" and automatically with the command, the changes will be updated in GitHub and your project will be ready to deploy.

ng deploy

In your repository on GitHub, click on “Settings ” navigate to “Pages”

Now, you can see that the "gh-pages" branch is available, and it is responsible for building our project so, select it and click on "Save".

In a few minutes, your project will be running!

If you found this article helpful, please leave a comment.❤️

How to export collection in Postman

Cinthia Barbosa da Silva — Tue, 26 Mar 2024 22:51:38 +0000

At some moment in a developer’s or QA’s life, it is necessary to use Postman to test requests, monitor, and design APIs. In this case, in my first article in this community, I would like to share how to export a Postman collection in JSON format.

Let's go!

Exporting a collection
To export a collection, first, it is necessary to salve your test creating a collection, by clicking "Save".

After it is created, it will be available on the left side, along with the collection name and related files.

Click on the ellipsis (...) and locate the option 'Export'.

When you select the 'Export' option, the Postman will inform you about the exported file extension, which will be in JSON format. Choose the 'Collection v2.1' option and click on 'Export'.

In a moment, the file will be downloaded to your computer.

With it in hand, you can share it with members of your team, import collections, or even share it on GitHub.

Try out Postman today and explore many other features. If you found this article helpful, please leave a comment.❤️