Mel's Take-Aways: #30daysoftesting

"Happiness lies in the joy of achievement and the thrill of creative effort." 

- Franklin D. Roosevelt


I found the exercise of #30daysoftesting a great way to think of other day-to-day things that I know I automatically apply my testing process to. While I wasn't successful at completing all of the challenges, I did a large number of them. A few I posted out on twitter and some I kept to myself or took notes of for future reference. 

Here are some of the highlights from the #30daysoftesting I enjoyed:

#2 - Take a picture of something you are doing at work - This was probably pretty creative for many of us that have NDA agreements. Mine was happenstance since I was installing SQL manager on Windows 10. I had a lot of woes that day, but I worked them out. 

#7 - Find an accessibility bug - While I didn't find a bug exactly, this was the inspiration, along with the movie Finding Dory to write something more about accessibility problems and issues with software and how they handle disabilities. 

#10 & 16 - Attend an event/ Attend a non-testing event - If you haven't heard or seen a tweet from me talking about Women Who Code or Chick Tech, look these two groups up. They are all over the world and they are doing great things for tech in general. One of my most inspiring moments came from doing a lighting talk at a Women Who Code meetup. 

#14 -  Step outside of your comfort zone - I've been working on FreeCodeCamp.com. I recently finished my first project for it, which is a tribute page for Sally Ride. I'm going to share it here, as sort of a double down on #14. It has been really hard for me to take time to code. Even then, I borrowed a lot from other people's work, but the modifications are my own. I just like playing when I have time and learning as I go along.

#17 - Find and share a quote that inspires you - If you missed the quote from Peter Welch, I suggest looking up his blog. It's pretty epic and funny.

#28 - Summarize an issue in 140 characters or less -  I'm wordy. I think I tried and failed to do this several times and ended up with multiple tweets. Ah well. 

Overall, while I wasn't able to completely get through all the challenges, I loved this idea, and I loved the attention the testing community gave to this idea. I hope it comes back around again, and gives us all more to learn and talk about down the road. 


Comments

Post a Comment

Most Read Posts

Ready, Tester One? *GO!*

"I handed my passport to the immigration officer, and he looked at it and looked at me and said, 'What are you?'" - Grace Hopper (60 Minutes Interview) The Grace Hopper quote above always makes me think about my job as a tester. Companies that develop software know they need testers, but they generally have hard time figuring out what testers are and what skills they need in the role. There have many discussions about how testers can be more technical and at some point, coding comes up in the conversation. My response on twitter contained a few things on a list I have, which I created for a client, so they could have a checklist of skills. This checklist was a guideline to determine the skill level of the tester applicant. This is by no means a complete list and I would be open to additions to the list. Feel free to add those to the comments or tweet them to me. For clarity, I took the list of skills I had and broke them into levels. I like games and I lik
Read more

Learning From Failure: The Tricky iOS Environment

"You build on failure. You use it as a stepping stone. Close the door on the past. You don't try to forget the mistakes, but you don't dwell on it. You don't let it have any of your energy, or any of your time, or any of your space."  - Johnny Cash There are times when our work, as a team, as testers on a team can give us insight into how we can improve things for the overall success of the product. Often those things are issues or defects which can present themselves at the most inconvenient times, in the most inconsistent ways. When we can learn from them and improve things for everyone on the team, the team benefits. When the team owns the defects and the testing strategy, not only the testers, then customers benefit as well. I was working remotely verifying a release and only had simulators and emulators to work with as I was testing mobile builds. Often folks mistrust builds which only use emulated software and not real devices for fairly good reasons
Read more

Postman In The Pipeline: Newman Delivers

Image
  It's not me, it's the songs.  I'm just the postman,  I deliver the songs....  - Bob Dylan Recently, I've had the chance to work on a project with some other awesome folks which has involved creating a BFF - A back end for front end service. This allows the app to access several API and aggregate calls into something the app can use, or lets the app send information to the BFF for several APIs to receive. Part of the code coverage for the BFF was creating some simple tests with Postman around the business logic and interactions. Learning About Postman I did lots of reading. Lots of reading how others has done things (Danny Danton - big props for being a super help!). Eventually, I came down to a small set of tests which could give us some accuracy about our BFF pipeline and the APIs we were accessing with it. Postman has a couple of options for this, global variables, environmental variables, and plain variables. One of the first problems I came across w
Read more