eliasnogueira

Title

5 Tools Java Developers can use to deliver High-Quality software

Description

Do you find it difficult to choose the right library to decrease the time you spend fixing bugs in your code? This talk will help you to not waste time presenting 5 tools to add additional test coverage at different levels of your application, each with a specific tip about the tool and its implementation via code. Now the levels of unit testing, integration, API and Web can be easily tested with these 5 tools.

Elevator Pitch

Choosing tools and/or libraries to increase test coverage and delivering reliable software is difficult because there are already several libraries with the same purpose, but with different ways of use.

eliasnogueira

Title

How to create modular microservice test projects

Description

The world is now full of distributed micro-services, generating different types of applications: the ones you are using to browse your social networks, to help professionals spend less time on repetitive tasks, and even to save lives.

We learned that testing the API layer with different approaches brings several benefits but also a complexity that can be measured in code duplication, high maintenance costs, and error-prone tests.

To solve this problem, in terms of how to test it, we can apply the same logic applied in microservices development: isolating them.

eliasnogueira

Title

3 Design Patterns and Architecture Decisions you must use in your project  

Description

Have you ever found yourself in a situation where your code was highly maintained, requiring a high investment of time to find out what doesn't work? One of the starting points to solve this problem is to adopt design patterns and architectural decisions that will allow us to create better and more reliable tests.

The process to create any type of test at any level is not an easy activity. It's even harder when we cross the unit testing line to test other levels like integration, API, Web, and Mobile.   We can benefit and solve many problems by adopting simple solutions with known design patterns, good architecture decisions, and the right libraries.  

eliasnogueira

public class FirstTest extends BaseWeb {
    
    @AfterAll
    @Override
    public void quitBrowser() {
        // empty or add your implementation
    }  
  
    @Test
    void firstTest() {

eliasnogueira

public class SecondTest extends BaseWeb {
    
    @Test
    void secondTest() {
        // the test goes here
    }
}

eliasnogueira

public class FirstTest extends BaseWeb {
    
    @Test
    void firstTest() {
        // the test goes here
    }
}

eliasnogueira

public abstract class BaseWeb {

    protected static WebDriver driver;

    @BeforeAll
    static void webdrivermanagerSetup() {
        WebDriverManager.chromedriver().setup();
        driver = new ChromeDriver();
        driver.get("http://eliasnogueira.com");
    }

eliasnogueira

public class SecondTest {

    private static WebDriver driver;

    @BeforeAll
    static void webdrivermanagerSetup() {
        WebDriverManager.chromedriver().setup();
        driver = new ChromeDriver();
        driver.get("http://eliasnogueira.com");
    }

eliasnogueira

public class FirstTest {

    private static WebDriver driver;

    @BeforeAll
    static void webdrivermanagerSetup() {
        WebDriverManager.chromedriver().setup();
        driver = new ChromeDriver();
        driver.get("http://eliasnogueira.com");
    }

eliasnogueira

public class ExplicitlyWaitExampleTest {

    private WebDriver driver;
    private WebDriverWait wait;

    @BeforeClass
    public void preCondition() {
        WebDriverManager.chromedriver().setup();
        driver = new ChromeDriver();