Skip to main content

Getting to Explore: WSL2!

https://www.pexels.com/photo/black-and-white-laptop-2740956/

Photo by Prateek Katyal from Pexels

 

Working on a graphical interface system is a delight, but every once in a while, I want to return to the command line style of computing - it's fast, and can have impressive results for a system. Even before Windows came up with a full subsystem, having a virtual machine and a Linux terminal for using some things wasn't uncommon.Thankfully, the Windows Subsystem for Linux (WSL) now exists, and is mature enough to handle most things. And once I experienced this style of computing, and the knowledge that most things were as simple to do with command-line terminals, I want to go back to the command line often.

 But being invited to see how much use replay.io would be for a tester helped make this choice easy. Not only did I get a chance to return to a method I enjoy, but a new tool that could help communication between team members. And, now that I think about it, with stakeholders and others that want a visual look at how a project is working, to minimize rework.

I knew I had this on my system at one point, so this wasn't totally new to me. And the changes from WSL1 made the process much easier. I made it through the steps - my chosen distro of Ubuntu is installed. 

Now to get replay.io installed!The steps to do this for Windows are not obvious - I located them in a Notion.io document, under construction at the moment. Since this is still in beta, I suspect that more-complete directions will be easier to find.For now, however, this is a great place to start.

One of the delightful, and yet frustrating things about WSL: it's a minimal installation. This does not take up as much space on the computer as a full second operating system would, but it also means that you need to sometimes install packages in ways that Windows users don't expect. And they are a very different thing than installing a new 'app' on Windows. 

cURL isn't difficult to do, but sometimes finding the correct package is a challenge. For me, looking in https://packages.ubuntu.com was the fastest way to ensure that the correct, newest versions were installed. And the small thrill of getting a command line item to work for the first time can be its own reward.

The Notion instructions are wonderful, and written to be easy to follow. But I ran into a missing item, and was getting Error: no DISPLAY environment variable specified This seems to be another missing library. After exploring a bit further, the documentation now notes that this is a Windows Insiders build. But, there are directions elsewhere to add a graphical interface without this build. I think I will take the time and explore this option, since I have no current plans to move to Windows 11.


More soon!

Labels:

Popular posts from this blog

30 Days of Postman - for Testers!

  https://www.pexels.com/photo/white-and-brown-cat-lying-beside-a-laptop-and-toys-5468268/ Photo by Karolina Grabowska from Pexels   Working with developer- focused tools can be a challenge for some testers: we may know what the words mean, but haven't used those skills recently enough to make the tasks simple. Or we may not have ever used them, other than at a quick glance to make sure that what we are getting matches what it should be sending. And some give results that require us to go find another team member to help interpret the results. Being a more-independent tester has always been one of my goals - being able to use the tools that are common in the team, and be able to do at least basic tasks that support my tests with them. Our team used Postman for many of the API tasks that we had, so exploring this tool was a natural fit. There are alternatives it there, both graphical and command line, so feel free to explore! The items that you can do, and tools that ...
Read more

Drop-down values for injection

cover_image: https://www.pexels.com/photo/flat-lay-photography-of-gold-iphone-on-opened-notebook-beside-pen-583847/ canonical_url:  --- Photo by Jessica Lewis 🦋 thepaintedsquare   Learning in public is grand, and when you have a team that is willing to help with something that seems simple, but you fall into overthink for the wrong items, it can really help to type out your thoughts, actions, and what the program does to frustrate you. And in this case, getting a value I could see in the debugger was the issue The automation needs to check for page elements – and the drop-down selector triggers potentially different elements. Plus, depending on the user logged in, there may well be different options available in that drop-down. Then, I can get the options available for the user on the drop down, get their values, cycle through them, and verify each set of elements on the page. My test account for this has four options on the drop-down, so I budgeted a couple of hours to get ...
Read more

Redefining my Role

Confession: I am a nice person. I'm the one that will check on people - and be concerned if someone is acting off. Or donate money to make sure the potluck I can't attend has everything it needs. This has had an effect on my career: I was less willing to point out 'in public' errors in the code or things that just felt off to me while testing. And this stopped me from being the best tester I could be. Trying to be kind to someone that was having a rough patch, or simply not wanting to expose them to a potential attack was both me trying to get things correct, but care for them. I've decided to embrace this aspect of myself, and shift my focus. Being 'nice' to the product, or company must include being the voice for both end users and the team. Finding things that will be difficult for them, confusing, or flat-out wrong is a major part of my job. And this was also one reason I don't 'delight', at first, when something doesn't work as expected:...
Read more