Mate Ajduković

One of the most common question during the interview for QA position is - What is your "favorite bug". Here are some interesting examples of bugs that could occur in an e-commerce platform: 1. The Infinite Discount Bug: A pricing calculation error allowed customers to apply the same coupon code multiple times, potentially reducing the price to zero or even negative values. 2. The Midnight Order Glitch: Orders placed exactly at midnight were assigned to the wrong day, causing issues with inventory management and delivery scheduling. 3. The Currency Conversion Catastrophe: A decimal point error in currency conversion led to items being sold for a fraction of their intended price in certain countries. 4. The Phantom Inventory Bug: Cancelled orders didn't properly return items to inventory, leading to "out of stock" messages for products that were actually available. 5. The Review Time-Travel Issue: A timezone handling error allowed users to post product reviews with future dates, making them appear at the top of the review list indefinitely. 6. The Cart Abandonment Amnesia: User's abandoned carts were being cleared unexpectedly, losing potential sales and causing frustration for returning customers. 7. The Free Shipping Fiasco: A logic error in the shipping calculator offered free shipping on extremely heavy items, potentially costing the company significant amounts in shipping fees. 8. The Search Engine Snafu: A bug in the search algorithm caused results to be sorted by price from highest to lowest instead of relevance, affecting user experience and potentially sales. 9. The Mobile Checkout Maze: A responsive design flaw made the "Confirm Purchase" button unreachable on certain mobile devices, preventing order completion. 10. The Infinite Loading Loop: A caching issue caused product pages to enter an endless loading state for users with certain browser extensions enabled.

14

Occasionally, I come across the idea that QA is a bottleneck. Like, that's a bad thing. But, consider this scenario... You are preparing for an important event. You check the mirror, and your outfit, you make sure you smell decent as a human being. All checks are green. Then, a friend or a significant other walks behind you and notices a string hanging from your backside in an unfortunate area for a string to be hanging. Would you prefer the person stop you, act as a bottleneck, and tell you what you missed? Or, would you prefer that the person didn't say anything, letting others see what you missed? I don't know. Sounds like being a bottleneck isn't a bad thing to me! #QA #qualityAssurance #software #riskAssessment #failureIsFeedback Photo by Jill Burrow: https://lnkd.in/edkHJXeP

44

20 Kommentare

Is Being a QA Risky? I recently read a discussion on the risks of being a QA, and here's what stood out: Workplace Culture: It's super important. Avoid places with a blame game mentality. Being in a supportive environment where everyone knows you can’t catch every bug is crucial. If the culture is to put blame on QA, run away if possible and let them enjoy that toxic environment. Dealing with Guilt: Missing bugs can make you feel bad, but it's impossible to find everything. The goal is to catch the big, risky issues and keep improving. *Exhaustive testing is impossible* if you went through the ISTQB syllabus. Team Effort: QA isn’t a one-person show. It’s about the whole team. It's not just on you – everyone has a part to play. To share the things not only eating the cake, but also when to take responsibility. Focus on Learning: Testing is about understanding the product better, not just finding bugs. Good testers help the team prevent issues in the first place and make the process better. Be everywhere. Starting from requirement refinement. Be Honest: If you miss a bug, just be honest about it. Explain what happened and how you'll adjust your approach. This builds trust and helps everyone improve. Remember, when something is missed, it’s a collective oversight, not just an individual’s. Follow the live discussion: https://lnkd.in/dZi6p_NQ

5

Dear engineers, Let's take a moment to appreciate the backbone of product quality: SDETs and QA professionals. Despite their essential role, they often face visibility challenges within companies. But why is that? And how can we change it together? 🔍 Perception Shift: It's time to recognize that SDETs and QA pros are not just support roles but experts in test automation, debugging, and more, extending beyond traditional testing. 💬 Team Collaboration: By bridging the gap between development and testing teams, SDETs and QA pros become part of decision-making and project planning, allowing synergy to thrive. 📚 Living Product Encyclopedia: With unparalleled product knowledge, SDETs are invaluable resources for architects and development teams. They possess deep insights into product architecture and design, serving as a crucial bridge between testing and development phases. ✨ Recognition Boost: Let's shine a light on their invaluable contributions. Acknowledging their diverse skills and providing growth opportunities empowers them to excel. Together, let's elevate the role of SDETs and QA. #sdets #workculture

112

1 Kommentar

👏 I couldn't agree more with these valuable insights on the software development lifecycle! I'm thrilled to see others discussing the importance of shifting testing left—a concept our company has been advocating for years. It's great to witness more teams learning, teaching, and integrating this approach. 1️⃣ Review Requirements Early: Even if you don't fully embrace shifting left, having your QA team review requirements before any code is written is crucial. QA can catch missing assumptions and unrealistic acceptance criteria early, saving you thousands of dollars in rework. Encourage your QA team to ask questions and push back when necessary. 2️⃣ Integrate Development and Testing: Development and testing should be a seamless, integrated process. Developers should test their code locally with both automated and manual tests. When features are pushed to a test environment, QA should be involved from the beginning, understanding the decisions that went into the feature to better assess risk. This collaborative approach minimizes wasted time and effort and reduces the risk of missed issues. Let's continue to champion the shift left approach and improve our development processes together! For more insights on how to effectively integrate these practices, reach out to our team. We're here to help you implement these strategies and achieve higher quality software. #ShiftLeft #QualityAssurance #SoftwareDevelopment #DevOps #Testing #Collaboration

5

2 Kommentare

🚀 Offering services for creating and setting up test automation from scratch! My name is Oleksandr Sotnichenko, and I am a QA engineer and programmer with many years of experience in test automation. If your company needs an effective test automation system, I am ready to help! 🔧 My key skills: Creating test automation structures from scratch Working with Java, JavaScript, TypeScript, and Python Optimizing test performance Using modern tools and frameworks 🌟 Why choose me? Deep understanding of testing and development processes Ability to quickly and efficiently implement automation Individual approach to each project Experience working with various teams and projects 💼 All costs are discussed individually because each project is unique, just like your deadlines! 😅 If you want to improve the quality and speed of your product development, feel free to contact me! Ready to discuss the details and offer a solution that suits you. I also provide consultations — write in personal messages or leave comments. 📹 Check out an example of my work here: https://lnkd.in/dEv9fgDn Best regards, Oleksandr Sotnichenko #testautomation #QA #development #automation #testing #softwaretesting #testautomation

1

You know you're a QA engineer when: - A failed test brings you more joy than a good movie. - "But it works on my machine" is the soundtrack of your life. 🎶 - You've become the office’s Chief Breaker of Dreams and Master of Edge Cases. - You know that behind every “tiny fix” is a universe of potential chaos. 🌌 Remember: If a feature works perfectly, did it even get tested? 😅 #QAEngineerLife #BugSquad #BreakingItBetterThanWeFixIt

11

At nearly every startup and scaleup, I’ve seen one (unfortunate) consistent failure pattern from great Testers: 1 - They try to convince their companies that QA/testing is really important and interesting in hopes of getting enough budget to do QA “right” 2 - They take on too many responsibilities with a wildly understaffed & under-resourced team 3 - They get overwhelmed by reactive testing requests, and because of 1 + 2, they don’t make a ton of progress… 4 - They burn out – What’s the solution? When Testers have brought MuukTest in to take repetitive testing, build &/or maintain their automated regression testing suite: 1 - They DON’T have to try to twist arms and make big promises to get big budget increases 2 - Because the tiresome work of repetitive testing, and forever test automation & maintenance is handled for them, they can focus more narrowly upstream on deep testing and quality during the development process 3 - They don’t have to convince anyone that QA is important; everyone FEELS the impact of QA 4 - They don’t burn out Advice for any Testers out there: If you are struggling to manage the MILLION different priorities of an understaffed QA/Testing department, ask yourself these 3 questions: 1 - What is the most tedious and non-strategic work I could take off my plate? (My opinion: Repetitive manual testing, struggling forever creating & maintaining regression test suites) 2 - What is the most strategic & impactful work I can double down on? (My opinion: Getting involved earlier in the development process, with deep and exploratory testing) 3 - Who can I get feedback on 1+2 from? (DM me! Happy to connect and give advice.)

8

Getting back to linguistics. As mentioned some time before, reflexive verbs in German made me think about testing and analysis. ) "Reflexive" is a nice word per se, doesn't it make you think, reflect as is? Lots of things can be reflexive, not only verbs. Graphs, relationships (mathematical ones, mind you! unless you want to reflect on yours, of course). Reflexive verbs loop on themselves, return back to the action with a pronoun meaning the subject does smth to itself. As many things in German, they form frames, i.e. the verb and the pronoun surround a bunch of other additional words bringing meaning. There is no direct counterpart to this grammar structure in English though. It is more straightforward, there are very few "looping" grammar constructs in it (maybe prepositional verbs where you separate the preposition from the verb and put it at the end of the question? it is no longer modern English I guess). What does it all have to do with testing and analysis, you ask me (or not)? Looping always causes extra considerations. The limit on the number of iterations. How many times are you going through the loop when covering your state-transition graph with tests? One time will suffice to ensure edge coverage, but is it really enough? What about the requirements, are there any constraints on the number of times something can be done and then returned to the initial state? There are sometimes, often dictated by security (preventing brute force attacks) but not only. This aspect is in many cases invisible, overlooked: those involved in test design don't ask (deciding on the number of iterations in tests themselves), those involved in requirement elicitation and documenting don't specify. Nevertheless, it's something worth reflecting, what would you say? Let your state transition graphs be complete (from business logic perspective, not mathematical one, mind you!). #intellivoice

7

For the past year, I have had to interview many candidates for QA positions, and I’ve been noticing something surprising during interviews: many candidates still talk about Selenium 3 when asked about their experience, even though Selenium 4 offers so many advancements and has been available for quite some time now. If you're in the automation space, it's essential to know the key differences and why switching to Selenium 4 is a smart move. Here are some reasons: ✨ W3C WebDriver Standard Selenium 3: Used the JSON Wire Protocol, leading to compatibility issues between browsers. Selenium 4: Now follows the W3C WebDriver Standard, ensuring better compatibility, stability, and efficiency across all major browsers. ✨ Relative Locators 🧭 (New in Selenium 4!) Selenium 3: Required explicit locators like By.id or By.xpath. Selenium 4: You can now locate elements relative to others! Find elements above, below, to the left, or right of a reference element, which is super handy when locators aren't obvious. ✨ Actions Class Enhancements 🖱️ Selenium 3: The Actions class was more verbose and complex. Selenium 4: The syntax is more streamlined for performing actions like drag-and-drop, making interactions cleaner and more efficient. ✨ Native Support for Chromium-based Edge 🌐 Selenium 4 now fully supports the Chromium-based Microsoft Edge, a much-needed improvement over the legacy version supported by Selenium 3. ✨ Enhanced Wait Mechanisms ⏳ Waiting for elements is smoother and more intuitive in Selenium 4. With enhanced timeout handling, you can now use the WebDriverWait class with Duration, which improves the syntax and reliability. 🚀 What does this mean for you? Staying on top of the latest tools and features, like those in Selenium 4, is critical for senior roles in automation testing. And based on my personal experience, it will help you stand out among other candidates. If you’re still relying on Selenium 3, it’s time to upgrade and take advantage of these powerful features. #CODIKUP #Selenium #AutomationTesting #QA #Selenium4 #WebDriver #TechCareers #TestingTools #ContinuousLearning #QALead #CareerGrowth

48

3 Kommentare

This post could have been written a year and a half ago. AI will not replace testing. But in a fundamental way, it *displaces* quality assurance. In one sense, AI is just ordinary software, running on machinery. In another, it’s an especially problematic kind of software. The algorithms that drive it have been generated with less and less human intention, deliberation, expertise, and social competence. Generative AI produces output that has even less of those things. "I'm seeing more and more people post about it on LinkedIn." If you look now, you might see hints that the world is starting to wake up, coming to its senses, and realizing that it had a little too much boozy koolaid to drink over the last few years. And you can’t spell "koolaid" without AI. More than ever, software development is going to need serious, sober, responsible testing to help it to drive safely. https://lnkd.in/eVwUTyQa

29

1 Kommentar

𝗖𝘆𝗽𝗿𝗲𝘀𝘀 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘁𝗲𝘀𝘁𝗶𝗻𝗴 When I held Jmeter training for my colleagues I got a question "Can we measure client side performance with Jmeter?" The answer unfortunately is: no, we cannot. QA engineers quite often focus on server side performance testing. We are not concerned about rendering of the elements because we have a subjective feeling that it is not taking that long. The truth is, web applications could have problem with rendering images, loading of Javascript files, large CSS files and many others. How can we measure client side performance? One of the tools we can use is Google Lighthouse. How does Google Lighthouse work? What is the difference between client and server side performance testing? What else can we test with Google Lighthouse? How can we simplify and automate the Google Lighthouse tests with Cypress? Check out my latest blog post for easy step-by-step setup of Lighthouse with Cypress and Javascript. I write about QA stuff. If you want to know how to get the best out of your automation tools follow me, visit my blog and subscribe to my newsletter. #qaessentials #cypress #testAutomation #automationTesting #lighthouse #performanceTesting #devTools https://lnkd.in/eCjizzxa

4

👋 Hey QA friends, who here is a fan of ChatGPT? 🤖 Drop a comment below and let’s connect! 🚀 On November 12, I’ll be speaking about "The Future of QA: Integrating AI for Intelligent Test Management" at an online event hosted by PractiTest - Test Management! 🚀 I’m excited to share insights on how QA professionals can leverage AI in daily testing activities to boost productivity and drive impactful results. From automating repetitive tasks to enhancing insights, We'll explore AI’s transformative role in test management and discuss how embracing these emerging technologies can shape the future of QA. Looking forward to connecting with you all at the event!  #QualityAssurance #AI #SoftwareTesting #Productivity #TestAutomation #FutureOfQA

49

10 Kommentare

Every time I talk with CTOs about Software QA and testing, I get one of two reactions: 1 - I don’t want to think about QA/testing; can we talk about anything else? 2 - I don’t want to think about QA/testing, but I now HAVE to focus on it, so can we please get this over with? This is a big reason why MuukTest sells *very* fast. Because when CTOs HAVE to focus on Software Testing, they want a solution that just… works. Something they can rely on, that they don’t have to think about too much, that they don’t need to know every single detail about. Is this the ideal world? Of course not. Do I WISH I could talk for HOURS with CTOs about QA and testing, about shifting left, about the nuances of *real* QA and different testing approaches? Of course. Do I feel like my 20+ years of Software QA/testing expertise is valued? Definitely not *until* we’ve delivered a ton of value for companies. And even then… nobody wants to hear my thoughts on QA/testing 😆 I can complain about this… or we can just build our business around the reality that CTOs don’t really want to talk about or think about QA/testing—they just want it effortlessly. Can you blame them for it? Of course not. 

25

8 Kommentare

Today I'd like to give a huge shout-out to my husband, 💻 Mariusz Mościcki who landed his 1st full-time role as a QA! 🎉 For those of you who don't know Mariusz - he's my biggest supporter and the best partner I could ever imagine to have! While I was going through my career change to become a Software Engineer, he became a stay-at-home dad so I could dedicate 100% of my time on learning. He was always there for me and never said "no" to some of my craziest ideas :) This is why I'm so happy and proud of him that he was able to make a career switch as well and land a QA role at the Xfaang team! Piotr Zientara, thank you so much for beliving in Mariusz na giving him a chance. For those who are interested, here's a little bit of a sneak peek from Mariusz's journey: - he started from joining the uTest where he first attended their academy. Once he got the basics and fullfiled minimum requirements, he started receiving invitations to paid projects, - in the meantime I was helping him with learning the ecosystem - the Browser Developer Tools and VS Code became his best friends. We also spent many hours preparing for an interviews, so he would feel more comfortable during the discussions with the interviewers/hiring managers, - he was applying for a QA roles in Prague and Czechia (we lived there for 3 years), but despite being invited to the interview process, he couldn't land a job, - he had mamy moments where he considered stopping going through a career change and become a bus driver (there's a huge demand for them now), - once we moved back to Poland he started applying for a roles there - still without a luck. He was getting interview invites, submitting tasks, but being mostly ghosted, - he first interviewed with Xfaang many months ago and back then he wasn't selected. He stayed in touch with Piotr while continuing polishing his skills and landed a short collaboration with the company. Later he did a 1-month internship with them and after that was offered a role! Please join me in congratulating Mariusz on his career change 🤗 #MondayMotivation #CareerChange #CareerChanger #QA #CareerSwitch

179

31 Kommentare

Next article in my weekly feed findings 🤖 Together with the author of this article, let's figure out The Art of Test Case Writing: Finding the balance (detailed VS concise) #qa #softwaretesting #softwaretesting101 #qualityassurance #networking #article #exploratory #testing #bugcount #testcase #balance #weeklyarticle

3

🤓 It's not hard to hire a senior developer You're just not offering them what they want. I posted a survey in a Slack group with devs, asking this question: "Would you as a senior developer be open to change jobs NOW if you can work 100% remotely?" (Btw, many of them are social and will come to the office more often. They just want true flexibility and quality of life. And to be fair, they want to do what they love, which is coding, with the minimum amount of interruptions.) Although the dataset is small, the results are interesting. 💸 38 % are willing to take a lower salary if they can work remotely ❓ 17 % would join a company that has some financial uncertainty if they can work remotely 😑 41 % would take a job with a less exciting role, product and techstack if they can work remotely This is an incredible opportunity to hire some seriously great engineers. Especially if you: — Can't pay the highest salaries — Don't build spaceships or AI agents — Are located in a small town or rural area Are there tradeoffs and challenges with (some) remote team members? Of course. But I just can't understand why more companies are not willing to take some risk here. You might regret this when the market turns upwards again. 🕺🏻

105

43 Kommentare

𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗱𝗼𝗰𝘂𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻? 𝗡𝗼 𝗽𝗿𝗼𝗯𝗹𝗲𝗺 As a QA engineer I used to work on a number of projects which my team inherited from other teams. Some of those projects were inactive for years before we started working on them. In these situations it wasn't unusual to have a poorly documented project. I had no idea how the system works, what to expect as output of my inputs. I had to be resourceful and find ways to better understand the logic behind the system. Over years this experience turned into an interview question which I find now quite often in various lists of common interview questions for QA positions. My latest article is my experience converted into words. You can find out how to test software without documentation.  Where to start?  What would be the common places to look for more information?  Where you can certain information about proper functioning of the software? How to expand your findings and discover more test cases? What is the desired outcome of such testing? I write about QA stuff. Visit https://qa-essentials.com, follow me and subscribe to my newsletter so you wouldn't miss any of the insights. #qaessentials #noDocumentationTesting #manualTesting #exploratoryTesting https://lnkd.in/eZ5dqEZw

26

3 Kommentare

At the moment, LinkedIn is once again seeing a wave of posts on the subject of "Why is the software methodology xyz actually called xyz? Wouldn't abc be a better name? We should rename it!" If something is already established and recognised by millions of developers and testers, why waste energy on such questions? By the way: for me personally, renaming always makes sense if the old names have negative connotations and/or can hurt people. For example, ‘mob programming’ to ‘pair programming’.

10

9 Kommentare