Weekly Webtips
Published in

Weekly Webtips

No more boilerplate code for properties files

We use properties files all over for our development to store configurable data of our applications and the same is true when it comes to test automation. We store config params in properties files.

Photo by Ferenc Almasi on Unsplash

Properties files store data as key-value pairs similar to a Java map data structure. Below is an example of a properties file.

server.host.name=testing.com

--

--

--

Explore the world of web technologies through a series of tutorials

Recommended from Medium

Dockerizing Your First Flask Application

Get Forex Data With PHP | TraderMade

What are bug examples in software testing

Life as a Engineering Fellow @ Urspace Labs

Animojis of Emi, Drshika, Nina and Eva

Kafka for dummies and with practical failure experiments

How to mine DERO: using CPU on Linux

Two years using kotlin and still having NPE?

Algo Trading for Dummies — 3 Useful Tips When Storing Trade Signals (Part 2)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Sajitha Pathirana

Sajitha Pathirana

Tech Enthusiast, SDET | Test Automation Consultant, and a Product Designer. I write about QA Trends, Testing, and Test Automation.

More from Medium

Cypress vs. Selenium Web-Driver

CodeBuild: Automated tests using Cypress

Testing API integrations

“You are mixing async and sync code”- Fix in Cypress