What I hear, I forget. What I see, I remember. What I do, I understand. -Xunzi
I wrote briefly about my experience taking my Red Hat class and trying to rally my classmates to create a study group.
Rather than going super hard on ansible, I’m taking it a section at a time. It’s easy for me to get really excited about a new topic, not see any progress, burnout, and never see or use it again.
Last Saturday was my last class.
I haven’t done any testing in a while. So much so that I’ve dropped down from Silver to Proven. I’m still interested in testing, but I needed to take a break.
Now that I’ve gotten into the groove of testing weekly, I’ve been upgraded to Silver. At this point, I’ve somewhat stopped focusing on my previous Test or Flop goals, and just dove into stretching my testing muscles.
I was on Twitter recently and signed up for a swag giveaway, but they were giving away more than they bargained for.
I joined a testing team for a popular streaming service.
I’ve reached this weird space in my exploratory testing where I think I know what I’m looking for, but I’m coming up short and thus I feel like I don’t know what I’m looking for. An exploratory dry spell, if you will.
I haven’t done much of the exploratory testing as I would’ve like to, but I have gone through a few structured test cases. As I spoke about in the previous month, I’ve been reading The Complete Software Tester and I decided to learn more about APIs and SQL. To be more specific, I decided to learn about SQL injections (SQLi) because I didn’t understand how they worked.
I wanted to see how far along I’ve come in my testing journey, so I’ve been looking at my tester stats. From June 2022 to today (5.25.23), I’ve done a combined total of 70 surveys, test cases, and bug reports.
I took a pause on the Test or Flop series, however that doesn’t mean I’ve stopped testing or flopping.
We’re at the end of the first season of Test or Flop, and if we only look at the results of the payouts, we might consider it a flop. However, despite not reaching our monetary goal we:
| Description | Reward |
|---|---|
| Completed test case for website | $15 |
| Total | $15 |
Sometimes a bug isn’t considered a bug. Before embarking on this testing journey I read a few blog posts and watched a few Youtube videos of testers discussing the importance of not getting too attached to bugs. Or, at the very least, don’t take it personally if they aren’t viewed as valuable.
| Description | Reward |
|---|---|
| Created a bug report for a podcasting app | $12 |
| Completed UX feedback of a security platform | $120 |
| Created a bug report for a website accepting an invalid email address | $3 |
| Created a bug report for a user being unable to decline marketing emails | $3 |
| Created a bug report for a members club not recognizing enrollment | $3 |
| Total | $141 |
| Description | Reward |
|---|---|
| Received a bonus for participating in a test | $10 |
| Completed a test case for a website | $20 |
| Total | $30 |
| Description | Reward |
|---|---|
| Completed training test case for a credit card | $7 |
| Created a bug report for missing icons on a webpage | $1.50 |
| Completed test case for a biometric app | $40 |
| Completed a test case for a DNS check | $4 |
| Total | $52.50 |
I’ve been testing on UTest heavily recently and I’m enjoying some of the projects I’ve been invited to. Just to be completely transparent, it’s not big money, so don’t go out and think you’re going to make it sprinkle after a week.
My posts finally appear the way that I wanted them to.
A few weeks ago, I was inspired by Alan Richardson’s Automating in the Browser course. Not only did it show me the power of the browser and JavaScript, but he also broke down the process of identifying html elements, creating reusable methods and then extending it to work automatically. Because of that, I thought to try it out on the testing website I started with for UTest.
The fun part about building a website is the journey to figure it out. This also gives me active problems to solve to stretch my knowledge of HTML/CSS/JS and how they work together. I have the gist on Jekyll and GitHub pages, but currently I can’t get my site to render blog posts properly. At the moment the homepage and the blog page are behaving as they should, but check this out…
This is blog number ∞ of ∞. As I learn things in QA, Software Development, or things that I’m generally interested in techwise. I’ll put them here. I tend to find myself in the learning phase, so this is intended to move me into the doing phase. As I read books, blogs, take courses, etc., I’ll use this space to track my progress.