David K.

Are you a QA/tester looking for work? You might like today's email. You might like it even more if you've used Tosca before. It goes out at 12 CST, so if you miss it, it's gone forever (ok fine, not really, you can just ask me to send it to you later lmao) (link in bio and/or comments below)

14

1 Comment

I'm interested Partick how one gets into games testing obviously you love it and it shows. but from.someone who spends about 30hours a year on any games console. How do you test a game, you can't get a games dev to package something up and pop it onto CD for.earch RC so in terms of PS3 games testing, I'd have a go at guessing it would be tested on an emulator? I'm not asking for.trade secrets, (they are secret after all). let's get your profile out there, let's show how you can take your experience and use it as a platform to mentor, to adapt and be a great asset. #opentowork #QA #gamestester #OpenToWork #GameTester #GameTesting #QAEngineer #GameDev #QualityAssurance #GamingIndustry #VideoGameTester #GameJobs #GamingCareer #GameDevelopment #HiringNow #GameTestingJobs #GameQA #RemoteWork #QAJobs #GameDevJobs #VideoGameIndustry

a few quotes from the article. "with 20 years experience as a Software QA, I had around a 2.5% chance of getting a QA job in Q1 of 2024." "The secret to getting a QA Job in 2024 is rising above this competition." "The secret to getting a QA Job in 2024 is being the 100% perfect fit." not agreeing with the last one. but 100% agreeing with the 2nd one.

11

1 Comment

❓ Why did I choose the QA profession? This question comes up a lot - why QA? Wouldn't it be cool if you got into the medical field? 🤔 My response: <a chuckle> I'm sure a lot of QA professionals have faced this question. Some testers even ask themselves this question. To those testers, I feel for you. Wishing you all the best in finding and achieving your dream job. As for me, I ♥️ my profession. Here's why I picked QA: ✅ Product quality can make or break a company’s reputation It's great to be able to contribute to the success of the company by shipping high-quality products. 🔧 The opportunity to work with a wide range of technologies and products Every product, project, and release has its challenges and requires a different approach, and I love learning fast and adapting. 🤝 QA is a collaborative field I enjoy working with developers, product managers, and other team members to ensure that the products we ship are of the highest quality and meet user needs. 📚 Continuous learning and growth Tools and methodologies are constantly changing in the QA field. I'm all about learning new things and staying up to date. Certifications like the AWS Certified Cloud Practitioner and ISTQB® Certified Tester Foundation Level reflect my commitment to learning. How can you not love this? 😍 What made you choose your profession? What keeps you motivated and inspired? Let's hear about it! ✨ #QA #field #Tester #Product_quality

7

This is a good conversation that is developing from a colleague’s comment on his timeline. For those who don’t know, the term #SDET (Software Development Engineer in Test) came into existence to recognize that there are members of the #QA Team whose principal role is to design and implement automation. The world and the SDET roles are always changing, and new technologies and tools change the ways that we all do our jobs. I also want to point out that this is a great reason to be part of LinkedIn. I can’t think of any other environment (including X) where professional conversations can be (mostly) separated from the everyday fluff of other social media. LinkedIn has its issues (and some strange behavior by some members), but I’m always glad when it helps me to reflect intelligently on important topics that have a bearing on my professional life. #SoftwareDevelopment #SoftwareQualityAssurance #SoftwareQA #testing #automation

3

Test Plan vs Test Strategy: 1. Test Plan: What it is: A detailed document that explains what to test, how to test it, and who will do the testing for a specific project. Example: If you're testing a mobile app, the test plan will say things like: We will test login, profile update, and notifications. These tests will be done manually and automated. Testing will start on October 1st and finish by October 10th. The team will include two testers and one test lead. 2. Test Strategy: What it is: A high-level document that outlines the overall approach and goals for testing, often used across many projects. Example: The test strategy for an organization might say: We will use automation testing for regression tests to save time. Our focus will be on functional, performance, and security testing. We will use specific tools like Selenium and JIRA for all testing projects.

4

I'm currently researching the top software testing conferences to attend in 2024/2025. I've compiled an initial list, but I'd love to hear your recommendations as well! What are the must-attend QA events this year in your opinion? What makes them stand out? Some conferences already on my radar include: 1. Agile Testing Days USA 2. EuroSTAR 3. TestBash Brighton 4. STAREAST 5. QA or the Highway But I'm sure there are many other fantastic options out there. Please share your recommendations in the comments below! 🙏 Thanks in advance for your input! #QAConferences #SoftwareTesting #QAExperts #QAEvents #QANetworking

27

13 Comments

❓ Why did I choose the QA profession? This question comes up a lot - why QA? Wouldn't it be cool if you got into the medical field? 🤔 My response: <a chuckle> I'm sure a lot of QA professionals have faced this question. Some testers even ask themselves this question. To those testers, I feel for you. Wishing you all the best in finding and achieving your dream job. As for me, I ♥️ my profession. Here's why I picked QA: ✅ Product quality can make or break a company’s reputation It's great to be able to contribute to the success of the company by shipping high-quality products. 🔧 The opportunity to work with a wide range of technologies and products Every product, project, and release has its challenges and requires a different approach, and I love learning fast and adapting. 🤝 QA is a collaborative field I enjoy working with developers, product managers, and other team members to ensure that the products we ship are of the highest quality and meet user needs. 📚 Continuous learning and growth Tools and methodologies are constantly changing in the QA field. I'm all about learning new things and staying up to date. Certifications like the AWS Certified Cloud Practitioner and ISTQB® Certified Tester Foundation Level reflect my commitment to learning. How can you not love this? 😍 What made you choose your profession? What keeps you motivated and inspired? Let's hear about it! ✨

167

25 Comments

🔍 Key Testing Types Every SDET Should Know 🌟 Here’s a breakdown of essential Pre-Production, Post-Deployment, and Release testing types, as well as the environments in which they’re applied. ⚙️ Pre-Production Testing Executed in environments such as Dev, QA, and Staging. 1. Unit Test: Tests individual components or functions for correctness. ➡️ Level: Dev/QA/Lower environments 2. Contract Test: Ensures APIs behave as expected and maintain contract agreements between services. ➡️ Level: QA/Staging 3. Regression Test: Verifies that new changes haven’t broken existing functionality. ➡️ Level: QA/Non-prod environments 4. Smoke Test: A quick, initial test to ensure that basic functionalities are working. ➡️ Level: Dev/QA environments 5. Sanity Test: Narrow testing to verify that specific changes are functioning as expected. ➡️ Level: QA/Staging 6. Acceptance Test: Validates the system against business requirements (often automated). ➡️ Level: QA/UAT environments 7. Benchmark Test: Measures performance against predefined standards. ➡️ Level: QA/Staging 8. Usability Test: Ensures the application is user-friendly and intuitive. ➡️ Level: Staging/UAT environments 🔄 Post-Deployment Testing Executed after deployment in lower/mirror environments. 1. Integration Test: Tests how components interact within the system. ➡️ Level: Staging/Non-prod environments 2. E2E Test: Ensures complete user workflows function as expected from start to finish. ➡️ Level: Staging/Non-prod 3. Load Test: Validates performance under expected user loads. ➡️ Level: Non-prod environments 4. Component Test: Focuses on individual parts of the system to ensure they behave correctly. ➡️ Level: Non-prod environments 🚀 Release Testing (Pre-Prod Blue Env) Tests before releasing to production. 1. Traffic Monitoring: Tracks incoming traffic patterns for anomalies. ➡️ Level: Pre-Prod 2. Error Logging Review: Analyzes logs for unexpected behaviors or errors. ➡️ Level: Pre-Prod 3. Abnormal Behavior Detection: Using tools like Kibana, Grafana, etc., to spot any irregularities. ➡️ Level: Pre-Prod 📊 Post-Release Testing (Prod Green Env) Executed after the system is live for all users. 1. A/B Testing: Compares two versions of a feature to see which performs better. ➡️ Level: Production 2. UAT (User Acceptance Testing): Tests in a live environment to ensure end-user satisfaction. ➡️ Level: Production 3. Traffic Monitoring & Error Logging: Continuously monitored using tools like Grafana and Kibana. ➡️ Level: Production 4. Chaos Testing: Introduces random failures to test system resilience. ➡️ Level: Production 🔑 Conclusion: Different testing types are used at various stages depending on the requirement and release management. • Dev Env. • QA Env. • Staging Env. • Non-prod Env. • UAT/CAT Env. The goal is simple: Dev Env. (feature creation/enhancement) ➡️ QA/Non-Prod/Staging ➡️ Rigorous Testing ➡️ Production Env.

1

Automation testing isn't just about speed. It's about empowering your QA team to innovate. Here's what I've learned. 1. Automation handles the routine ➡️ Testers tackle complex scenarios 2. Consistent test coverage ➡️ More time for exploratory testing 3. Faster feedback loops ➡️ Quicker issue resolution 4. Reduced human error ➡️ Increased overall quality 5. Scalable test suites ➡️ Better equipped for growth But remember: Automation complements human expertise, never replaces it. The real magic happens when you blend both. How are you balancing automation and manual testing in your projects? #QualityAssurance #TestAutomation

5

1 Comment

Key Tips for Functional QA Interviews I've noticed numerous threads where QAs are searching for jobs, so I thought I’d offer some insights from my perspective on what interviewer typically ask for in a functional QA role. While there may be slight variations depending on the interviewer, the core context remains consistent. It goes without saying that you need to articulate your thoughts clearly, organize them well, and be able to justify everything listed on your resume. Please avoid simply copying and pasting tools and technologies without genuine understanding. For functional QA role, we typically ask the below questions: 1. Explain the project a.) application - feature, functionality, architecture b.) your role in the project - typical day-to-day, responsibilities etc. 2. Types of testing a.) functional - smoke, regression etc... b.) difference between above, when it is typically used in the testing cycle with example (if possible) 3. Given any random feature think of possible and exhaustive test cases a.) organise your test cases ( or thoughts) in different logical categories of testing. b.) not to forget data validations while thinking about test cases 4. Knowledge of mobile app testing - ecosystem awareness (if you have mentioned in your resume) 5. Knowledge of backend testing at a high level (what is API, error codes, a bit of POSTMAN, etc if you have mentioned in your resume) 6. Some knowledge of debugging #interviewtipsforQA #interviewinsight #manualQA #testinginterview #QAJobs #QAInterviewTips #FunctionalTesting #QACareer #QualityAssurance #QATesting #SoftwareTesting #MobileAppTesting #BackendTesting #QADebugging #QA #SQA

307

26 Comments

What testing doesn’t do: Prevent bugs What testing does do: Prevents oblivion to bugs that weren’t prevented What testing is: 1. Quality Analysis 2. Quality Assessment 3. Quality Awareness What testing is not: Quality assurance See more below in the original post. This reminds me about a time when I explained a dev manager that QA is supposed to be quality assurance and not quick assurance. the explanation was not well received :)

2

1 Comment

You keep writing sloppy Selenium automation tests. ⭕ low quality ⭕ unstable ⭕ hard to understand ⭕ needing a lot of maintenance For a while, no one notices this until the day when your tests are used in a pipeline after a new build is deployed. Then, since your tests fail a lot randomly, the doubts about your work start. Why do you need to fix these tests? 🤔 Why do you need to keep working on them? 🤔 Why are they not stable? 🤔 Assuming that you have lots of similar tests, management will need to make a decision on how to go forward. ❎ should these tests be improved?  ❎ should these tests be redone? ❎ should they hire someone else? ❎ should they outsource the test automation work? ❎ should they buy a codeless tool? you may say that there is still hope for you. you can improve these tests. you can redo them. chances that you will be allowed to fix a situation that you created are low. because this will take such a long time. so, at this point, you wont be in a good spot. this is where writing sloppy Selenium tests leads. you will lose your job, one way or another. the solution is simple (not easy though): do better. https://lnkd.in/gcqtETFa

3

adding a few more :) Andrejs Doronins ☑ never do code reviews ☑ never refactor code ☑ automate as much as you can in a single test method ☑ write the tests at multiple levels (page methods, test class methods, workflow methods, web driver methods) ☑ bigger is better, have huge classes and huge methods ☑ any code that needs to be reused should go to a utility class, inherit from these utility classes ☑ generate test data through the UI ☑ do not keep in touch with the dev team, never tell them about what you do ☑ be a hero (the test should work even if the site doesnt)

9

3 Comments

My recent QA job search observations 😅 ⬇ Here are some things I've noticed during my job search (spoiler: not all of them are negative, many of them are quite positive or neutral/surprising): - Some companies manage the hiring process with just one HR screening call and one 1-1.5 hour tech/team interview. They don't need 3, 5, or 7 stages to make a decision. - Many companies hire QA Engineers without live coding sessions - good one 👍 - Some companies have live coding sessions just because top IT companies do - just wasting time and resources on useless conclusions 🤷‍♂️ - There are some long online tests - technical, logical, coding, and personality/cultural fit tests. Why? 🤷‍♂️ - Some companies don't understand who they need or what problems the person will solve. They want QA team leaders and QA managers with fresh, strong programming skills. For example, a QA Manager with excellent communication, leadership, and managerial skills but not an expert in JS/TypeScript and C# isn’t considered a fit. - Some companies look for passionate, enthusiastic unicorns willing to work almost for free and miss good candidates while trying to find the "ideal one" they can't and won't find. - Companies want QA experts with broad experience and tech knowledge but offer tasks that don’t match this level, with colleagues having mediocre skills and compensation not matching responsibilities. - Many companies avoid responsibilities by hiring short-term B2B contractors without perks or job security, yet expect passion, involvement, strategic thinking, and care for the company's future. - Many HRs and recruiters are very professional, know their stuff, and conduct real interviews with tech experts. - Many interviewers are very chill, making the interview feel like a friendly conversation between professionals (this is really cool) rather than a technical interrogation. - Almost no cringy questions. - The hiring process in many companies is very slow, taking a couple of months from application to decision, leading to candidates likely accepting other offers in the meantime. - Many companies believe that it's okay to pay much less than 2 years ago for the same work just because the market is tough now - a kind of meaningless approach. - No one cares about the #opentowork green banner 😄 - Some interviewers are very inexperienced in interviewing and try to play "big bosses and superior experts". - Lots of mismatch in job ads - titles, responsibilities, skills, and salary ranges are mismatched very often, sometimes 2-3 different roles are mixed in one with a title which means another role and salary of junior-mid level tester. - Candidates ghosting is a real thing for sure. - Some recruiters are just spammers. Probably, they are the ones who work for some staffing agencies - a very inefficient way to hire anyone with their help. - Interviews with the upper management/CEOs are the best and the worst 😅 #jobsearch #hiring #qajobs

112

23 Comments

I was amazed last night at how polarizing the following idea apparently is in parts of the software testing community: You may not _always_ need a formal bug report in order to “report” a bug. Personally, this just seems like common sense. Consider examples outside of work—do you “always” write things down on a grocery list in order to get them? Or do you sometimes make a mental note, or remember something when you’re at the store, or ask a family member as they’re heading to the store, “hey, can you get Oreos?” Same with work around the house, right? How many people formally document _every_ problem that needs to be fixed? (Yes, there’s always that one person who will raise their hand. I mean normal people 😆.) Of course there are potential problems with those less formal approaches. We even joke about it with t-shirts like “When I say I will fix it, I will fix it. There is no need to remind me every six months.” But life would be pretty stale if we treated every interaction as requiring formal paperwork to move forward. Don’t get me wrong—sometimes bug reports are mandatory. Maybe it’s a product where every customer-reported defect is legally required to be documented and dispositioned. But I suspect in the vast majority of cases, it’s perfectly ok to (gasp!) wave a developer over and ask “is this supposed to happen?” and for them to cock their head, stare for a minute, then reply “give me a second—I can fix that.” Remember: Testing is activities, not artifacts. “Individuals and interactions _over_ processes and tools.” There is often value in the processes and tools, but not when they’re treated as a substitute for teamwork. #softwaretesting #criticalthinking

22

24 Comments

🔹 Onboarding. What 3 things I try to tell every new hire 🔸 When a new tester joins our team, I always start with a few principles that go beyond the job description. These aren’t just tips - they’re the foundation of great QA work. Rule #1 Question the status quo Great QA isn't just about following test plans. It's about asking, "Why are we testing this way?" Your fresh perspective can uncover inefficiencies and spark innovations in our testing processes. Rule #2 Collaborate across boundaries QA doesn't exist in a vacuum. Engage with developers, product managers, and even customers. Understanding different viewpoints leads to more comprehensive testing strategies and better software quality. Rule #3 Embrace continuous learning The QA field evolves like crazy. Dedicate time each week to learn a new tool, technique, or technology. Whether it's exploring AI in testing or mastering a new automation framework, your growth directly impacts our team's capabilities. 🔔 There are so many more helpful rules we need to share with the new teammates, but these three always stand out for me. Respect those who look up to you. 🙇‍♂️ #QAtips

27

2 Comments

In the software industry, #QA professionals sometimes refer to themselves as "bug hunters"! Is that true? 🤔 The story of the term "bug" originated from a real event in 1947. Engineers working on the Harvard Mark II computer found a moth trapped in a relay, which was causing a malfunction. Grace Hopper, one of the pioneering computer scientists, famously documented this in her logbook, labeling the issue as a "bug." As for QA professionals referring to themselves as "bug hunters", this is more of an informal industry term and part of the #QA #culture in #software #development. Many QA testers adopt this phrase due to their role in identifying and fixing errors in software. 👇 https://bit.ly/4dLwy9U 👇

22

4 Comments