Eduardo Maltez: Full-system testing using Selenium - Episode 224

Azure DevOps Podcast

Eduardo Maltez is a Software Engineer at Clear Measure. He has extensive experience in .NET, including Blazor, SignalR, Azure Service Bus, SQL Server, and all kinds of automated testing. Earlier in his career, he apprenticed under Jeffrey Palermo and is currently building automated full-system tests for a large and complex software ecosystem at one of his clients.

Topics of Discussion:

[3:09] How Eduardo got into programming and the steps he took to make it a full-time career.

[8:04] How Eduardo makes the decision in his head when he needs to use Selenium vs. other tests.

[10:52] Eduardo talks about ShoWorks and the technology components behind it.

[16:27] What does it mean when a test is brittle, and what do you do to make tests that are not brittle?

[18:41] When a test is brittle, it means you can’t really rely on that test. Brittle tests are unreliable tests, in the end.

[23:36] How do you know when to stop a unit test?

[25:44] What are Educardo’s go-to methods for finding the right DOM element?

[33:26] When it comes to rough edges around Selenium itself, it’s not necessarily something that doesn’t work, but it’s something that definitely always causes just a sudden road bump in the test cycle.

Mentioned in this Episode:

Architect Tips — New video podcast!

Azure DevOps

Clear Measure (Sponsor)

.NET DevOps for Azure: A Developer’s Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon!

Jeffrey Palermo’s YouTube

Jeffrey Palermo’s Twitter — Follow to stay informed about future events!

Programming with Palermo

[e-mail]

ShoWorks

Selenium

WebDriver Wait Class

Want to Learn More?

Visit AzureDevOps.Show for show notes and additional episodes.