Git Product home page Git Product logo

test-automation-bootstrap's Introduction

Hi, I'm Sérgio 👋

Linkedin: sergiomartins8 Medium: sergiomartins8 Twitter: sergiomartins8_ GitHub sergiomartins8

Welcome! My name is Sérgio and I'm a Test Automation Engineer.


Here are some facts about me:

  • I don't simply report issues 🙅 I drive quality from the outset. I am passionate about quality, and I believe that my role starts well before development. Quality is the responsibility of the whole team, and it is my role to support everyone on the team to understand and live this.

  • I take pride in my automation because it helps my team go faster 💨 I write my automation code with the same care, skill, and craft as the best production code.

  • I believe that automation should serve the whole team and not just the tester 💯 I leverage automation not only to speed up my own testing, but to help developers deliver higher quality products faster, and to help business articulate their needs more precisely.

test-automation-bootstrap's People

Contributors

dependabot[bot] avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar

test-automation-bootstrap's Issues

Split into modules (ui-tests, api-tests, load-tests, utils, etc)

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

🐛 Logback configuration file not being applied

Description
Logback.xml configuration file is not being applied. It is not under the default package.

Additional context
Default path is under resources package.

Also, could be fixed with System.setProperty("logback.configurationFile", "path-to-file/logback.xml");

Add gitlab CICD pipeline example

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

☀️ Move to maven:archetype

Describe the solution you'd like to see applied
Boostrap the whole project from a maven:archetype command

Additional context

TBA

☀️ Add changelog

Describe the solution you'd like to see applied
Have a change log.

Describe alternatives you've considered
A CHANGELOG.md automatically updated.

Add contract testing

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Add stress testing

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

☀️ Add browser property

Browser should be used as a property when executing maven tasks

e.g.
mvn test -Dbrowser=chrome
mvn test -Dbrowser=firefox

Add healthcheck to wait for selenium grid before running tests!

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

☀️ Improve current default config management

Is your feature request related to a problem? Please describe.
The goal is to make it as CI/CD friendly as possible as well as easily manageable.

Describe the solution you'd like to see applied
Current configs are stored under properties files. The goal is to have default settings whilst allowing to inject the desired ones (which is currently being done, but kinda hard to understand and manage)

Describe alternatives you've considered

  1. Having a default properties file and remove de run.tests.local=true config ✅
  2. Having a static class that holds the current default properties

Add load testing

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

☀️ Generify Mocks

The mocks used by the annotation @Mock are currently interpreted as being static, i.e. as it is implemented on the MockListener.

The goal is to make it as generic as possible so that different expectations could be injected without changing the implementation details.

Add more ui test examples

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Add slack custom notifications!

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Improve documentation

Is your feature request related to a problem? Please describe.

  • Heartbeat/Monitoring documentation
  • Improve overall documentation and its structure

Add distributed testing reports with influx stack

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]

Describe the solution you'd like to see applied
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

🐛 Fix firefox integration tests

Description
It was detected due to #17 development.
Maven integration tests fail when using -Dselenide.browser=firefox

How to Reproduce
Create an integration test that uses firefox

Expected behavior
Tests should pass successfully

Additional context

  1. Fix mockserver initialization
  2. Fix firefox accessing mockserver expectation

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.