Skip to main content

Posts

Good thing He tested it

My husband and I both work in technology however he may have a different perspective as a software developer. I'm not very dependent on my husband for things. But I can name a few things here and there that I depend on him for and vice versa and our kids depend on each of us for different things. We have a 5 year old son and we have Apple TV. Our son knows how to fully operate this device with zero guidance. One day the remote stopped working. My son immediately said to me “Mama, the Apple TV isn’t working.” A side story: a while back the issue with the Apple TV was we couldn’t find the control and the world stopped. My husband said download the Apple controller app. We did and we found the control. So when the control in my hand showed no signs of life, I went to prove this theory that it was the control and the tv device. I launched the app and sure enough I could navigate and select my son’s show (Voltron). This is where the story gets interesting: I said to my husb
Recent posts

A double run because of no integration testing

Integration Testing is defined by Wikipedia as  " is the phase in  software testing  in which individual software modules are combined and tested as a group. It occurs after  unit testing  and before  validation testing . Integration testing takes as its input  modules  that have been unit tested, groups them in larger aggregates, applies tests defined in an integration  test plan  to those aggregates, and delivers as its output the integrated system ready for  system testing ." My friends decided they wanted to do a challenge for weight loss. We wanted to do something to capture both diet and activity to help us.  I found the mobile app 'Lose It '. This app integrates with other apps and devices such as the Apple Watch, Fitbit, and Nike Running. I went for a run Friday morning but indoors using the treadmill. I turned my Nike RunClub app on and ran.  I would hear the app update me along the way, "1 Mile, time blah blah". I'd look at the treadmill

When I grow up I want to be...

I wouldn't complete that phrase with "Tester". Nor SQA. Nor Quality Assurance. In fact, the idea of working in Technology was not even on my radar.  I wanted to work with children. That was my first dream job - child psychologist. As I looked for colleges, I stumbled upon a university that had a degree in International Relations. I didn't have Google back then but worked at a library and began researching careers with this degree. While in college, I had heard about those studying or majoring in Computer Science. The problem with that was science: it's not my favorite. So I stayed away from anything computer related and mostly used the Macs for those 15-20 page papers. I got a job out of college as a Project Manager. But it was in for the Technology department of a global trading company.  I had no idea about the projects I was managing; what updating an application entailed or testing the changes to the front-end of the application.  I had to manage status

Pass, Fail, Sort of

One of the first things I learned as a Quality Assurance Analyst more than 15 years ago was I had to mark a test Pass  or Fail . Green was associated with a test that passed and red associated with a test that failed. It seemed very black or white, but we all know that there is always room for some gray (or grey). I was taught to follow the steps in the test case and when done mark it Pass or Fail - the vast Excel spreadsheet would have the empty column labeled Pass/Fail. I'd follow steps like these: Write the words "This IS a tESt" Highlight "Test" Bold "THIS" Underline another word Expected Result: THIS  IS a tESt Actual Result:  This   IS a  Test And the test would be marked  Pass ...but is it? Is it  Fail ? Most of it Passes, there's just this one tiny detail. And that's the thing, the Detail. It wasn't until many more years of testing did the performing of the steps, the marking of the scenario Pass or Fail com

I'm going to

As a gift, I got a space to blog. I'm going to blog about    Testing.  Why? Because I've been doing it for quite some time now as my job.  It is also something people may do on a daily basis and not even realize the skills they're using are utilized by testers. I'd like to share the experiences I've had in my career and in turn encourage more dialogue, comments and questions about my experiences or your own. So here goes. Let's try...