Thoughts on technology, movies, and everything else
I work in technology sector. And I do round a clock, not only from 9 to 5. It is my bread and butter, it is my hobby, it is the fascination of my life. And with the current rate of change particular in information technology (IT), there is always something new to learn, to try, to talk about. I often post news, thoughts, and reviews. And when I do, this is the category I use.
Thanks to this great tip I’ve discovered the recently added Tab Groups functionality in Google Chrome browser. All you need to do is navigate to chrome://flags/ , search for “Tab Groups” feature, enable it, and restart your browser. Once that is done, right-click on any tab and you’ll see the option to “Add to new group”. Any tab that is already a part of the group, can be removed from there and added to any other existing group.
It is possible to rename groups and assign each one a color. In the screenshot above you can see how my groups look right now. Yellow ALT, red LM, blue PP, purple TTM, and green BLOG are tab groups. A color running under tabs to the right of each group indicates which tabs are part of the group to the left.
Grouped tabs are also a lot easier to move around and separate into a new browser window.
k6 is a developer centric open source load and performance regression testing tool for testing the performance of your cloud native backend infrastructure: APIs, microservices, serverless, containers and websites. It’s built to integrate well into your development workflow and CI/CD automation pipelines.
This is one of the better tools that I’ve seen in a long time. Not only it does its job great, but it integrates brilliantly with your development and testing pipelines.
You can either build your tests from scratch, or you can convert import them from your existing tools. For example, Postman collections, environments, and tests can be converted to k6 with postman-to-k6. Here’s a blog post to get you started on that path.
Side note: if you hit the “EACCES: permission denied, mkdir ‘/usr/local/lib/node_modules/postman-to-k6/vendor’” durin the postman-to-k6 installation, then simply append “–unsafe-perm=true –allow-root” to the “npm install” command, as suggested in this GitHub thread.