Skip to main content

Teaser

One of the reasons I started this blog was because of the increasing chance that many of you will find yourself in a 'sandwich', later in life, if not now. The lengthening of the life span of many people on the planet, plus having children later - and add to the fact that statistics show that many millennials will not have the opportunity to ever own a home - the chances increase that you will find yourselves living with parents and children at the same time. There are ways to do this, and stay sane - I hope to give some ideas of what has worked and not worked for me, personally.
*~*~*

It's been a time - so much has been going on that it feels like the day is over before anything productive can be done. The company my son works for has lost quite a few people - they pay a fairly low rate - and every year about this time, they end up needing to hire a new batch. Which is nice, in a way: he gets a larger paycheck. But, it also is more hours, in a highly stressful situation, and never knowing which facility he will be sent to, nor what situation he will find when he gets there.

Mom is repeatedly opening a small wound instead of letting it heal; insisting she is not doing it, as well as becoming less likely to either hear me speaking. These, of course, are a major source of stress and drama right now - and there's really not much that can be done about it. So I stay silent, unless it's urgent.

The good thing about being quiet: I keep it up from habit now. I get to see more of the wildlife in the area. I'm not the type of female to squeal at a bee, nor a spider. As long as we don't interact too much. And the local rabbits and squirrels accept me as a mostly-sedentary threat.
Now, Pokemon in the neighborhood - that's another thing. :) But, we'll get back to that.

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

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