I like to work with managers who get their hands dirty to have something done, instead of asking someone to do the work.
Managers that exist to manage people shouldn’t be necessary for mature and autonomous teams.
Think about it. If there’s no one to perform the work, what’s the point of having a people manager? In the end, there’s no one to manage.
On the other hand, if there’s no manager, but the people needed to perform the work are there, it can still happen.
I imagine that people managers won’t like reading this post (if they’re ok being in their comfort zone)…
Before writing this content, I was reading about software composition, and I had this insight.
Such projects allow me to put into practice new knowledge acquired day-after-day, during study hours, to be ready when similar problems arise in work projects.
When the protractor-helper started, all the code was in a single file. Nowadays, the project is better modularized, tested, as well as…
Automated visual regression tests add a new validation layer in the software development life cycle, ensuring that when application changes break its visual appearance, you will have a quick feedback to fix it before your users even notice.
The course is available on Udemy. Check it out and learn how to create screenshot comparison tests in an easy way!
I hope you like the course, and I wish you a good testing journey! 👋
It is with great pleasure that I present you with the newest version of the protractor-helper library, which now provides a better experience for its users with type definitions in the functions’ signatures.
As of version 4.1.1, if you use the Visual Studio Code editor (or some other with TypeScript support), after importing the library into your test file, when you type something like helper.click(), you will be presented with the parameters that such a function expects, what types such parameters should have, which are mandatory and which are optional, in addition to the return of each function.
I’m happy to announce the launch of a new course on Udemy.
In this course, you will learn:
I have a theory (and some experience) that having fewer environments in the software ecosystem is better than having more of them.
It’s a common practice in many software projects to have:
In this course, you will learn:
I hope you like the course and your feedback is more than welcome.
Until next time, and happy testing! 👋
If you automate or intend to automate tests of web applications with the Protractor framework, protractor-helper will help you on making them reliable. It does that by using the ExpectedConditions class, from Protractor, to ensure that the test scripts will only interact with elements, or run assertions on them, when such elements are in the correct state, like visible, clickable, present, etc.
Automated tests of GUI (graphical user interface) are commonly seen as flaky. They fail when they should not, and so they lose credibility.
Have you already asked yourself why continuous integration is not providing value to your project or organization, even if you have all the tools and infrastructure needed for it?
Maybe the problem is in other stages of the software development life cycle, or in the process and the way the team works.
Because of this, we need to understand what’s the primary goal of this software engineering practice so that we can comprehend what to expect from it.
The purpose of continuous integration is to reduce the time between the development and the release of a working software update in…
QA Engineer, clean coder, blogger, writer, YouTuber, online teacher, mentor, member of technology communities and passionate for good music 🎶 and skateboarding