Skip to content
View renatograsso10's full-sized avatar

Block or report renatograsso10

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
renatograsso10/README.md

Renato Grasso

QA Engineer · Test Automation · Performance Testing

LinkedIn Email

About me

I'm a QA engineer focused on software quality, with an interest in the engineering behind reliable test automation. I work with web applications and APIs, combining automated testing, performance checks, and development skills to investigate failures and catch regressions.

My approach draws on SDET practices: treating test code as software, building reusable components, and integrating tests into CI pipelines. I care about maintainability, clear diagnostics, and choosing the right coverage for each test layer.

Areas of focus

  • Test engineering: reusable fixtures, page objects, and maintainable automation frameworks.
  • API testing: contract checks, response validation, and integration coverage.
  • Performance testing: workload design, load testing with k6, and analysis with Grafana.
  • CI and diagnostics: smoke and regression pipelines, reports, traces, and failure investigation.
  • Development interests: JavaScript, C#, Java, and development that complements my testing work.

Technologies

Testing & CI

Playwright Cypress k6 TypeScript GitHub Actions

Development

I use JavaScript and TypeScript for test automation with Cypress and Playwright, and also enjoy C# and Java. I'm interested in how applications are built alongside how they are tested.

JavaScript C# Java

How I approach quality

  • Start with risk. Focus coverage on important user flows and likely failure points.
  • Keep tests maintainable. Use reusable components and clear assertions instead of duplicating setup.
  • Make failures useful. Keep traces, screenshots, and reports that help explain what went wrong.
  • Test beyond the happy path. Include invalid inputs, API contracts, and behavior under load.

Contact

You can reach me on LinkedIn or by email.

Popular repositories Loading

  1. renatograsso95 renatograsso95 Public

    Forked from renatograsso95/renatograsso95

  2. renatograsso10 renatograsso10 Public

  3. auth-app auth-app Public

    Forked from samycici/auth-app

    Auth App example with express and node

    JavaScript

  4. recipe_api recipe_api Public

    Python

  5. codecrafters-http-server-rust. codecrafters-http-server-rust. Public

    Rust

  6. cypress-study cypress-study Public

    JavaScript