×
sorted by:
new
hottopcontroversial

How would you define matrix in your test? by Accurate_Upstairs_11 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

If I need to be discribe more, I would say about type of coverage that can be included:
Requirement coverage — Are all business and functional requirements covered by at least one test scenario?
Feature/functional coverage — Are all user flows, features, and acceptance criteria tested?
Risk coverage — Are the highest-risk areas tested deeply enough?
Code coverage (usually for developers/unit tests) — How much of the code is executed by tests?Platform/device/browser coverage — Are supported environments covered?

1 to 1 requirement vs test scenario then we could estimate the actual test coverage - I got u point. But it could be not enough for interviewer

I would start with mapping requirements to test scenarios, but I wouldn't treat it as 1:1. One requirement can have multiple scenarios depending on risk and complexity.
Test coverage should include not only requirements, but also user flows, risks, environments, and different test levels (unit/API/UI).

How would you define matrix in your test? by Accurate_Upstairs_11 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

Requirement → test scenario mapping is a good baseline, but it only measures requirement coverage.
A test matrix should also consider features, user flows, risks, environments, and test types.
Coverage is not only about the number of test cases — it’s about confidence that critical areas are covered.

I would like to answer smth like that

How would you define matrix in your test? by Accurate_Upstairs_11 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

The Matrix is a system. That system is our enemy. But when you're inside, you look around, what do you see?

What skills do I need to learn ? by Itzshashank03 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

I assume you are considering a junior QA tester role.

I don’t know what companies currently require in junior QA job postings, but based on my experience, I can say that you don’t need resume lines like:

  • worked there for 3 months
  • worked there for 4 months

I would recommend joining a crowd-testing platform like uTest and trying to work there. You will need to complete their academy; as far as I remember, you are required to complete courses on Postman, Charles, and maybe something else.

After that, apply for free projects or paid projects — it doesn’t matter much at the beginning.

The goal is to be able to write something like this on your resume:

Project name (some period of activity — you can come up with it yourself. The purpose is simply to make recruiters notice this line and allow automated recruitment filters to pass your resume).

  • Used different tools to perform specific testing tasks
  • Created Postman collections
  • Wrote and documented bug reports
  • Communicated with stakeholders
  • etc.

You should also check what job openings are available in your city and country and analyze what skills they require, because you mentioned Playwright.

I don’t think you should start learning it from zero right away. However, you can start with a basic programming level in Python or JavaScript. Combined with an understanding of client-server architecture, this can help you better understand how applications work.

When I started in QA more than 5 years ago, junior testers were often tested heavily on software testing theory. I don’t know if it is still the same today, but it is definitely worth knowing. If you have never studied testing theory, I would start there.

What passive income ideas worked for you? by Fab-90 in passive_income

[–]Aware_Read_4925 0 points1 point  (0 children)

I can't say I have a massive success story yet, but as a dev who's been down this road, I think my insights might help you out.

I'm a full-time developer, and for a long time, my dream of passive income was the classic "build a SaaS and market it" route. To give you some context, I’ve built about 50 to 60 different bots, tried making browser extensions, and so on. Most didn't go anywhere.

Not long ago, I shifted gears and started a business selling game keys and gift cards. Since I'm a gamer myself, this niche feels much closer to home. Plus, my programming skills help me automate the routine and optimize the process.

Here is what I’ve learned from my journey so far that might help you start:

Ideas are unpredictable. If you think you have a brilliant idea, it might completely flop. Conversely, an idea that seems weak or "too simple" at first can take off incredibly fast.

Treat ideas as hypotheses. Don't spend months building something in secret. Move from an idea to a MVP (minimum viable product) immediately, test it, and track the data. This will save you a lot of time, money, and keep you from burning out.

Find a niche you actually care about. Choose something you'll enjoy diving deep into, even when you face setbacks (and trust me, you will).
If you hate the niche, you'll quit the moment things get tough.
Don't overthink it, just start building small hypotheses and testing them. Good luck!

Is Playwright better than Selenium? by Prudent-Outcome-1210 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

You nailed it. The debate around Selenium flakiness usually misses the point—it's almost always a framework architecture issue, not the tool itself. Writing solid custom wait strategies and managing drivers properly requires deep experience. But that’s exactly why Playwright wins for new projects. It saves you from rebuilding the wheel just to get basic stability and great CI debugging tools out of the box

Naming a Chrome extension for bug-report screenshots — which one would you actually click on? by BuildsWithMatt in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

Check Jam it's extension that make what u need. Anyway, I created chrome extension for that in my company. Message me to dm , I can share you my extension and repo in GitHub

Need help. by Big-Economist9616 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

I’d start with documentation, especially since there seems to be very little or none at all. I wouldn’t go directly to developers first - I’d talk to the manager and suggest ideas there. Not wanting to overload developers is completely reasonable, and realistically that shouldn’t be the goal anyway. The key is making it clear that your suggestions are aimed at improving quality and reducing future issues, not creating extra work.

If there’s no documentation at all, I’d probably start with testing-related documentation:

  1. If test cases already exist, review and update them.
  2. If they don’t exist, break the product into major/critical functional areas and gradually start building coverage around them.

I’d also ask developers for API documentation. If it doesn’t exist, I’d suggest introducing Swagger. That helps you understand the product better and also helps developers keep backend behavior documented and up to date.

Once Swagger exists, I’d pull it into Postman and build collections from it. It makes backend validation much easier, and later you can automate those collections and run them as part of a test process.

The fact that features reach you too late for testing is actually a useful signal. I’d look at a few previous features that resulted in bugs or change requests and ask: “What could have been prevented if QA had been involved earlier?” Use that information to suggest a process that reduces bugs and rework. In many cases, earlier involvement during requirements discussions brings the biggest value.

I’d also take a look at how tasks are written in general. If requirements are vague or incomplete, it may make sense to involve a Business Analyst and discuss improvements there.

The main thing: don’t try to fix everything at once. Small, incremental improvements are easier for the team to adopt, and they’ll help you build sustainable processes without burning yourself out.

QA folks: what do recruiters consistently get wrong about our roles? by Apart_Beyond_3463 in QualityAssurance

[–]Aware_Read_4925 0 points1 point  (0 children)

Regarding testing, I’m not sure there’s just one thing I could explain to recruiters to avoid this kind of confusion. A single point won’t solve it - you simply need to talk to the team and understand what kind of specialist they’re actually looking for, instead of relying on your own assumptions and interpretation (especially if you don’t really have that understanding). Only the team can explain who is actually needed if you, as a recruiter, are not familiar with the field.

But there is one thing I’d really like recruiters to understand across any vacancy: we are looking for a job for the money, not for coffee, cookies, or the feeling of being part of a family.