100 Days Of Code: Websites == Experience

Photo from https://unsplash.com/@markusspiske

Sometimes, life just doesn't go according to plan. Like this post, that should have been done yesterday. And is going to be choppy, since it seems that they need me more than usual right now.

I had been taken, literally, to visit a friend of my son - who owned a shop here in town. Okay, yeah, they have a Facebook presence (actually, two of them), but wanted more exposure. And so I was 'volunteered' to do a quick web page for them - and then offered, since I was doing one, I may as well do two, to the stylist that rented a part of their sales floor.

This was a mistake - trying to get communication with them is nearly impossible. I have rough ideas ready for both sites, but want some information from them. I'm about ready to give up - and use just random images from the internet.

That takes care of two of the sites - the third is a wonderful business in another state: a Mexican-Greek restaurant that is very involved in the community. I have a menu, and have made plans to return some time soon for another meal. This one is taking a while: I want this to be as unique and welcoming as the business is.

Making websites just to have on the portfolio has never appealed to me - there are so many small businesses that might be interested in having one, and getting to meet new people, and support the local community is always a pleasure.

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 ...

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 ...

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:...

Distorted Rovings

Search This Blog