Welcome to the 3rd edition of CodingJag by LambdaTest. Dan Lines mentions in his Rule 4.1 of Developers Constitution that If you’re caught enjoying yourself in a meeting you can get your dev card pulled.That’s ambitious! Developers run on a different timeline than others and meetings cost them more time, which reduces overall productivity. It’s important to evaluate meetings based on the value it would derive and draw the thin line between essential and non-essential meetings. Now that’s the tough part! Do check out this interesting story on “too many meetings” by Dan Lines and see how you can optimize your meetings.
A really deep dive into how Cypress can be used for testing React applications by Artem Sapegin. Loved the rich-in-code examples!
Elias Nogueira shares several ways that you can use to generate test data for automated tests, explaining it very simply with examples.
Automating end-to-end tests might block your team while they wait for builds to run. A few tweaks to your test automation workflow can help unblock them.
Too many meetings" is not a complaint. It’s a cry for help. Forget no-meeting Friday. It doesn’t work. Dan Lines have some new ideas you can use to increase dev focus time.
Bruno Oliveira explains why there’s no ideal test automation pyramid to follow and gives a piece of advice on how you should adapt your strategy according to the test architecture instead.
Here you’ll get the Recipe to pick right test cases for automation.
Chrome has a headless option. In that case chrome launches without an interface. There is an other way to do web automation in java with no browser.
Detailed info: https://www.lambdatest.com/newsletter/editions/issue3