Today’s Tip Tuesday article is about storing test data in the JSON file to improve and expand the diversity of tests in your automation.
You use Page Object Model to separate your tests from the pages to improvetest automation performance, but do you separate your test data from the tests? One way to improve and expand test automation is by keeping your test data (e.g. users, attachments, test content, etc.) in a JSON file that you can pull from. This allows you to create additional, diversified tests easily.
You may have noticed that I’ve been inactive for a while, from blogging and social media. A lot has happened and I needed to take some time off. I’m sure you were taught, like myself, that things happen for a reason. I don’t always believe that, but I will concede the time off helped me re-center. During this time, I took on some new challenges and meditated. I invested into myself and my family. Overall, I recharged. I even managed to take a vacation!
We all agree that branding is important to businesses, companies lose money when bad press comes out. How they respond can say more than the mistake or bad press. The same is true for your personal brand. Your personal brand is important to how you are viewed by people and companies. Your brand is more than your resume or LinkedIn profile. It includes, your online presence such as blogging and tweeting, in addition to your interactions with others in your industry. Whether it is big or small, everyone has a personal brand.
We all hate finding bugs. Like ants and spiders they get into everything. But also serve a purpose; ants fight termites and spiders eat other bugs. So can bugs in software be good? If you work in quality assurance or testing, they are good for business.
When I started out on my crazy adventures in test automation, I stayed close to the browser. The first automation framework I worked in was WATIR and it was awesome. It is a clean and straightforward framework which is what drew me to it. I was introduced to my first headless automation tool by one of our UI Engineers. The tool set was CasperJS and PhantomJS. While they were great tools, I really wasn’t sure how to use them correctly, especially since I wasn’t watching my tests execute anymore. So I played with them for a while and that was it.