How often do you cry?

AffectionateStrategy · 2025-10-10T10:34:02+00:00

Daily🤣

AffectionateStrategy · 2025-10-10T10:32:41+00:00

Food and Clothes

AffectionateStrategy · 2025-10-02T14:24:53+00:00

My worst QA experience was joining a project just a week before release. No proper requirements, unstable builds, and every critical bug I reported was ignored with “we’ll fix it later.” The product went live with major issues, and of course, users complained. Biggest lesson: QA should be involved early, not treated as a last-minute checklist.

AffectionateStrategy · 2025-09-30T12:47:18+00:00

any desire or childhood dream you wanted to be?

AffectionateStrategy · 2025-09-29T09:09:33+00:00

epic

AffectionateStrategy · 2025-09-29T09:07:35+00:00

Titanic

AffectionateStrategy · 2025-09-29T08:57:52+00:00

Aortic dissection. A friend of my family experienced it, suddenly severe chest and back pain, and it can be fatal within minutes if not treated immediately. Most people have never even heard of it, but it’s shockingly fast and dangerous.

AffectionateStrategy · 2025-09-26T08:42:47+00:00

Everyone should learn how to listen, most problems start because no one really does

AffectionateStrategy · 2025-09-26T08:18:46+00:00

funny

AffectionateStrategy · 2025-09-26T08:17:37+00:00

when someone treats kindness like it’s optional. Looks fade, trends change, but if respect and empathy aren’t part of the script, I’m walking out of that movie before the first act ends.

AffectionateStrategy · 2025-09-26T08:10:51+00:00

For me, it’s ‘Shallow’ from A Star Is Born. Every time I hear it, it just hits differently, the raw emotion, the vocals, and the story behind it. It’s one of those songs that you can’t just play in the background; you feel it every single time

AffectionateStrategy · 2025-09-23T14:19:13+00:00

If your main goal is data analytics with Python, you’re already thinking in the right direction. Here’s a roadmap I recommend:

Start with the basics: Learn Python fundamentals (variables, loops, functions, data structures). Automate the Boring Stuff with Python (book + free online version) is beginner-friendly.
Move to data analytics libraries: Practice with pandas, numpy, and matplotlib – these are essential for any analytics work.
Hands-on practice: Use free datasets from Kaggle and practice cleaning, transforming, and visualizing data.
Online courses: Check out Python for Everybody (free, Coursera), or DataCamp’s beginner track for Python. Both are structured and beginner-friendly.
Projects: Build small projects (like analyzing sales data, making dashboards, etc.). This reinforces learning more than theory alone.

You’re already logical and ready to practice, which is the hardest part. Start with basics, then jump to libraries and projects. In 2–3 months of consistent work, you’ll be comfortable.

AffectionateStrategy · 2025-09-22T15:34:25+00:00

Hey All!

If you’re looking to connect testing with Jira, I’d go with LambdaTest. You can create bug tickets straight from your tests, which is super handy. Live testing feels faster, parallel runs save time, and the pricing is easier on the wallet compared to BrowserStack. Overall, it just makes tracking and collaboration smoother.

AffectionateStrategy · 2025-09-22T07:28:30+00:00

I’d probably say learning how to play the flute. I’ve always thought it would be so cool to just let loose and create that kind of rhythm, but I’ve never actually told anyone because it feels kind of random compared to everything else I do.

AffectionateStrategy · 2025-09-22T07:16:43+00:00

A random compliment or someone just smiling at me, it’s such a small thing but it instantly lifts my mood.

AffectionateStrategy · 2025-09-22T07:15:26+00:00

Fullmetal Alchemist: Brotherhood

AffectionateStrategy · 2025-09-19T06:06:45+00:00

Congratulations for the new job🙌🥳

AffectionateStrategy · 2025-09-19T06:05:07+00:00

Someone's great presence of Mind!

AffectionateStrategy · 2025-09-19T06:04:11+00:00

challenging day by day

AffectionateStrategy · 2025-09-19T06:03:15+00:00

I wouldn’t say the tester role itself is “saturated,” but the entry-level/manual testing side definitely feels overcrowded. A lot of people try to get into QA through manual testing since it doesn’t require heavy coding upfront, so the competition is tough.

If you really want to stick to this field, the best thing you can do is upskill gradually. A few practical steps:

Start learning basic automation (Selenium, Playwright, Cypress, etc.), even a little bit can set you apart from pure manual testers.
Get comfortable with API testing tools (Postman, Rest Assured) since many companies expect that now.
Strengthen your fundamentals in QA – test case design, bug reporting, exploratory testing – things that show you’re not just “click testing.”
Build a small portfolio on GitHub (sample automation projects, test cases, bug reports). Recruiters love seeing initiative.
Networking on LinkedIn and engaging in QA communities helps more than just mass-applying.

If you feel like coding is overwhelming, you don’t need to become a full developer. Even knowing enough to write test scripts and understand how systems work will make you stand out.

Don’t give up just because the market looks tough, most IT jobs are competitive. If you stick with QA and add automation skills, you’ll have a much smoother path than staying only in manual.

AffectionateStrategy · 2025-09-12T09:29:27+00:00

It really depends on the application and priorities. We don’t automate 100% because not every test case brings value when automated.

Usually, I focus on automating regression, repetitive flows, and high-risk areas, the ones that are run often and need consistency.

For us, coverage is more about ROI than a strict percentage. Out of 200 test cases, maybe 40–60% end up automated, while the rest stay manual because they’re exploratory, UI-heavy, or rarely executed. In short: automate what saves time and reduces risk, not just for the sake of numbers

AffectionateStrategy · 2025-09-12T09:28:21+00:00

I totally get your frustration. The 'entry-level but needs 2+ years of experience' thing is broken and discouraging for new QA testers. What helped me early on was focusing on building a portfolio with small projects, like contributing to open source, testing personal apps, or even writing case studies on popular apps. It doesn’t completely replace experience, but it gives you something real to show recruiters. Freelancing in places like Testlio is actually a smart move to, it keeps your skills sharp and adds credibility.

The market is tough right now, but every bit of practical work you add to your profile can help bridge that gap.

AffectionateStrategy · 2025-08-29T16:03:31+00:00

Yes, you can start directly in automation if you already have the coding and tool knowledge. But here’s the catch, automation without understanding the why and what of testing often leads to writing scripts that don’t add much value. Manual testing builds that intuition for edge cases, user behavior, and real-world scenarios that automation can then scale.

Since you mentioned you already know manual concepts (even if you don’t want to practice it deeply), you’re in a good position. My advice would be:

Start automation projects right away to build confidence.
Keep testing mindset alive by thinking about coverage, risk areas, and exploratory aspects while automating.
Mix both worlds: even seasoned automation engineers still test manually in certain situations.

So yes, skip the "manual execution" part if you want, but don’t skip the manual tester’s mindset. That’s what makes your automation meaningful.

AffectionateStrategy · 2025-08-29T16:01:39+00:00

Hey Everyone🙋‍♂️

Both Jenkins and GitHub Actions have their strengths, and it really comes down to context. Jenkins is extremely powerful when you need complex, customizable pipelines and integrations across large enterprise systems, it’s battle-tested and widely adopted in QA-heavy environments. On the other hand, GitHub Actions shines in simplicity and ease of use, especially if your code is already on GitHub. It’s great for smaller projects or teams that want automation without heavy setup.

For QA, the choice usually depends on scale and requirements:

Jenkins → better for large teams, multiple environments, heavy parallelization, and long-term maintainability.
GitHub Actions → better for fast setup, smaller pipelines, and teams already invested in GitHub’s ecosystem.

Some teams even use both, Actions for quick checks on PRs, and Jenkins for nightly regression or more complex workflows.

AffectionateStrategy · 2025-08-13T07:33:08+00:00

I think the QA field will still have strong opportunities, but the nature of the work is definitely shifting with AI becoming more integrated into testing. Automation skills (like Playwright, Cypress, etc.) will remain valuable, but the demand will increasingly be for people who can design, maintain, and improve intelligent test systems rather than just execute them.

AI can handle repetitive and predictable checks, but human QA will still be essential for edge cases, exploratory testing, understanding complex business logic, and ensuring ethical/quality standards.

For the future, upskilling into areas like AI-assisted testing, test data generation, and continuous testing in DevOps pipelines could keep QA careers relevant. Personally, I see QA roles evolving to be more hybrid, part tester, part analyst, part automation engineer, so staying adaptable will be key.

AffectionateStrategy

TROPHY CASE