Aga Bailey

One of the most useful discussions you may get monthly , if you are interested in Software Architecture.

3

Just finished the learning path “Continuous Integration/Continuous Delivery (CI/CD) with Jenkins”! #continuousintegrationandcontinuousdeliverycicd

6

'But don't Cypress, Playwright, and Selenium have their own test reporters?' Yes, but qa-shadow-report offers something different. This reporter compiles native JSON test output into a Google Spreadsheet or CSV, providing your team with a free reporting tool that uses familiar, existing technology, with security concerns or workspace limitations in mind. What sets qa-shadow-report apart: - No dashboards: Use Google Sheets or CSVs that everyone already knows. - No subscriptions: Completely free. - No workspace access: No need for new tools or learning curves. - Simple configuration: Just a config file specifying your team's details. - Real-time access: The entire team can view and edit the spreadsheet as soon as the results are available, with no need to wait for access. Check out qa-shadow-report on NPM -> https://lnkd.in/gVXhvaBd Its open-source! -> https://lnkd.in/gKGFwaPE #cyshadowreport #npm #cypress #playwright #selenium #googlesheets #csv #opensource #softwaretesting #automation #reportingtools #freetools

4

Folks who work on an agile-style IT product team, curious on your thoughts on this as the conversation came up in my team's standup: Do you follow the general rule of thumb to point stories/tickets solely on complexity and not time? And if so, does it seem to cause confusion when trying to gain an idea of how long the ticket may take to complete (as leadership will look at sprint boards and have a general timing benchmark based on the point value)? Do you have any ideas you would propose, or your team has enacted, to assist in avoiding the confusion or tendency to use story points as an idea of how long it should take to complete the effort, since they are not pointed with time as a factor?

2

Turns out committing to a date and time works...(https://lnkd.in/gFeNd8nu) But for today, here are some thoughts on how to gently introduce change to yourself and/or your colleagues via time-limited experiments, possibly involving salads. https://lnkd.in/gEjKuKAz 🧪

7

💡 Real-World QA Lesson: It’s Not Just About Local Success! 💡 Ever been in this situation? A developer delivers a build for testing, but issues pop up. When addressed, the developer says, “But it works perfectly on my local setup!” The project owner then steps in with a truth bomb: "We're not building a product that only works on ‘your’ local environment!" 😏 This highlights a key principle in QA: A successful product works across all intended environments, not just locally. Testing is here to catch these gaps, ensuring a consistent, reliable experience for all users, not just developers. Lesson: Quality assurance is about real-world readiness, not isolated success. The goal is a product that performs reliably for every user, every time. Let’s keep testing and iterating until the experience matches the vision—beyond “just my local”! 👏 #ContinuousImprovement #RealWorldReady #QA #SoftwareTesting #QualityMindset 

6

Just finished the course “Postman Essential Training” by Kristin Jackvony! Check it out: https://lnkd.in/eEeGzypD #postmanapi #apitesting #testautomation.

6

This article will help to integrate the playwright bitbucket code in bitbucket Pipeline CI. #playwright #automationtesting #bitbucketpipeline

31

One of the cool things about contributing to open-source is that you not only get to give back to a community you are part of, but you get to learn from much way smarter people than yourself 😄 I started contributing to Selenium in November last year, and some of my contributions, with the help of really cool people, made it into the latest release 4.2.2 If you want to contribute to the Selenium project you can go to the Selenium organization on Github and find any project that you feel you can start helping out with: https://lnkd.in/dJpuvTAW If you want any tips or help on how to get started, since this is the stage that I'm in, feel free to ping me, I do not know much but I will do my best to help out 😅 Or if you want to ask the Selenium community, you can follow this page: https://lnkd.in/d6nyFwsU For an overview of the latest release: https://lnkd.in/dwPZC5KZ Thank you for reading, have a great day, and happy testing! 😊 #Selenium #OpenSource #Testing #Contributing

14

Navigating Software Bugs: Blame and Improve Bugs are opportunities for growth, not blame games. Embrace curiosity, investigate thoroughly, and focus on the root causes. The result? A more resilient software ecosystem and a healthier team dynamic. However, based on my experience, blame isn’t inherently negative. It’s how we wield it that matters. As long as we focus on improvement, foster collaboration, and maintain empathy, we can harness its power effectively.

25

2 Comments

About a year ago, I launched a Russian-speaking YouTube channel (https://lnkd.in/eUwiSVEU), which has grown to 75k subscribers. Although it began as a blog about my QA career, I haven’t posted anything related to that in over six months. When I started, I secretly hoped that content creation might be "my true calling." I was excited about the idea of turning this passion into a full-time endeavor, freeing me from the constraints of my previous career in Tech. A few months ago, I left my job, partly because of this new passion. Around the same time, I read a book called So Good They Can’t Ignore You. It made me realize: you can’t abandon a career and suddenly succeed at something entirely new just because you're passionate about it. It requires building what the author calls Career Capital — a set of rare and valuable skills you can offer to the world. Only AFTER that can you think about receiving something valuable in return. This approach worked for me as a QA engineer — a realization that only came to me after I attempted a career switch and read the book. I became skilled not because I was naturally talented but because I dedicated countless hours to deliberate practice and navigated many stressful situations, like sleeping just 4 hours a day and working 16-hour days during an onsite 3 week trip abroad to prepare a system for UAT. I hadn’t fully appreciated that these challenges and focused efforts were what helped me grow professionally. For my new activity — YouTube — I’ve poured approximately 400 hours into a single video (the most recent one). That’s totally OK because: 1. I’m new to scriptwriting. 2. I have no prior experience in video editing. 3. I struggle with shyness, often feeling extremely anxious when filming in public places. Despite these challenges, I want to become good at content creation. However, the biggest realization is how much I also want to excel in my primary field — QA. More than even I’m now willing to invest hundreds, even thousands, of hours into mastering the skills required to become a true professional. Ironically, while chasing what I thought was my “true calling,” I’ve come to understand that the only real “calling” is the pursuit of excellence in the work I’m already doing. Have you ever faced a similar realization about your career? I’d love to hear your thoughts!

91

12 Comments

Five Playwright CLI features you should know. https://lnkd.in/e9xdfZpG #softwaretesting #qualityassurance #testing #development #projectmanagement #ai

3

I am happy to share my latest blog post, focused on best SDLC practices, this one regarding the importance of well-documented requirements. What is your favorite story about requirements, either well crafted or perhaps lacking a bit? I bet that, like me, you could write all day on memorable examples. :) Note: non-software examples equally welcome; this transcends a single industry. https://lnkd.in/gcp_kbYe

9

4 Comments

I submitted a talk to speak at 2025 Automation Guild! If you want to hear me talk about why your testing framework is not the cause of your flaky tests please upvote on https://lnkd.in/exF4gTuE and upvote any others that look interesting!

17

I love this story about how exploratory testing will find bugs even with TDD, pair programming, and other techniques to reduce bugs. They’re still great techniques since exploratory testing won’t catch all bugs. I am confident that if you that if you give me software that has any complexity to it, I will find bugs regardless of the development process. I love the development processes that reduce the number of bugs, but I know they are still out there.

6

1 Comment

If you want to be a good intuitive Bayesian—if you want to naturally make good predictions, without having to think about what kind of prediction rule is appropriate—you need to protect your priors. Counterintuitively, that might mean turning off the news. —Brian Christian

2

Excited to share my latest blog post where I break down the basics of Rust, starting with the classic "Hello, world!" and then exploring the magic of Cargo, Rust's powerful package manager. Whether you're new to Rust or curious about what makes it tick, this post will get you started with a solid foundation. Check it out and join me in discovering the world of Rust! 🌍 #Rust #Programming #TechBlog #HelloWorld

6

What features do you want added to Playwright? There is an open issue where you can make any wishes you'd like to see added to Playwright!

28