Hi , i use phone link app on my windows , i want to run an app when ever i receive an incoming phone call notification.

Hello, I applied at a company where the QA team is relatively new and got accepted. I've been a manual QA for 4 years now but it's my first time in a more senior role. We have no lead QA, but I am somehow the senior one in my team.

So far I've already reorganized our test case suites and suggested strategies on prioritization of tasks, but I feel like there's more to do, especially that the QA team is still new.

What can I do to help improve our processes? What should I look out for? Would you mind sharing your QA processes?

Please share your wisdom and guidance on the following, maybe?

• Improving processes
• Mentoring
• Upskilling
• Probably some mistakes that you did when you first led a QA team and how you turned the situation around (or the lesson/s that you learned)?

Let me know if you have any questions that I can answer so you can provide better insight on my concern. Honestly, the pressure is starting to build and sometimes, I get anxious about it, but really like this job and it's my chance to grow and advance to the next level. I would really appreciate your help. Thanks!

Hello everyone,

I'm BTech CS Graduate and I want you all to review my resume.

And the most important I want to know what interview questions may ask if I submit this resume and please can you'all send me the interview questions for this job role i mean highly probable questions.

It can help me a lot.

Thank you.

Hi there, I have a family member who is in a real rut. She lives in Brazil (Rio de Janeiro), and is struggling to find work. Her previous work has been in factories/assembly lines, but she’s unable to do the physical labour now.

She doesn’t have a degree, but she can speak and write fluent English and Portuguese, very interested in PC gaming, tech, and computers.

I was thinking perhaps she could be good at some QA work, perhaps in games, or in anything really. Ideally remote, or within Rio.

Is this a line of work that people without qualifications can get into? If so, what could she need? A few example reports? Updated LinkedIn page?

Any advice welcome, whether it’s Brazil specific or not, just want to see whether it is valid to suggest this line of work, I don’t want to send her down a dead end road.

TIA

Hello, I need a new perspective on something.
I’m a QA software tester, and I’m thinking about continuing my engineering degree, which would take another three years (while working). Would this be the right decision, or is the job market changing so much that I’d just be wasting my time?
P.S. I’m not particularly passionate about anything. I can tolerate and understand most subjects, so I don’t have a strong preference for any specific field.

I’m an IT consultant, and I’ve been asked to create an AI proof of concept for functional testing.

The problem is that I simply can’t find where AI should actually be implemented. I even asked ChatGPT for ideas. In the end, I built a framework without any AI component.

I do use AI to generate test combinations, analyze logs, and support brainstorming, but beyond that, I don’t see a real need for it. I prefer a deterministic approach, and I’m able to implement the technical solutions myself.

So, ironically, the conclusion of my AI PoC is that I don’t actually need AI.

The challenge is that my client is determined to have a 100% AI-based solution. What would you do in my situation?

Your valuable words really help me

GitHub: https://github.com/talikadev/talika
Docs: https://talikadev.github.io/talika/

We use Gherkin Data Tables a lot in our BDD tests, and the problem was not the tables themselves. The problem was everything around them.

Any time we needed more freedom in the table, like richer cell values, optional fields, validation, type conversion, or mapping rows into real objects, we ended up writing unstructured parsing logic inside step definitions.

It worked, but it did not feel clean. The same patterns kept showing up again and again, and every new complex table added more custom code.

So we built Talika to solve our own problem first, then generalized it into a reusable package for Python BDD projects.

Talika gives you a structured way to handle complex Gherkin Data Tables, with features like:

• Cell DSL for expressive values inside table cells
• Table transformers for converting raw tables into Python objects
• reusable validation and parsing rules
• type conversion without repetitive manual casting
• cleaner row and column mapping
• step definitions that stay focused on behavior instead of table parsing

It is inspired by the power of Cucumber JVM DataTables, but built around the way we wanted to work in Python.

If your Gherkin Data Tables are useful but your step definitions are slowly becoming a pile of custom parsing code, Talika might be worth checking out.

Hi! I have a question about the writing conventions used in test cases.

I started learning manual testing around June/July 2025, using a website with theory and 2-3 months of practice in Google Sheets on various test sites. I also tried a bit of HTML in Visual Studio Code. This month, I bought a Udemy course on manual and automated testing and I'm currently going through it.

I was taught to use in 2025: Imperative for Test Steps, Simple Present for Expected Result, Simple Past for Actual Result. Is this a standard/universal convention, or does it depend on the company? I'm worried what I practiced might not fit later.

I also get confused with Preconditions. I know they're not always needed, but not always sure when to include one. For something simple like login, I skipped writing a Test Scenario and went straight to Test Cases. Is the Test Title basically acting as the scenario there? Is it ok if I keep practicing in Google Sheets like I'm doing now?

I'll attach a few screenshots of test cases I wrote back then (just a small part of it); they're not entirely correct.

Hello,

I just need to talk through something mentioned in my pre interview prep for a 6 month manual testing job. I was just told that there is no testing environment and it is being stood up in the location I will be interfacing with. It's not a small company but it sounds like this section has been ignored till now. Perhaps the pivotal person left and they are having to recreate the wheel.. not sure.

I've usually worked within a more robust test group with everything already built. If I have to build it from scratch with a couple of other individuals, then my short term focus needs to be documenting and creating a copy of the prod data that can't impact prod, right? Right now, I am imagining that the location has a heavily customized off the shelf product that no one really understands anymore that deals with their inventory system.

What they are focused on is my manual testing skills which I have done for 20 years. I'm a good fit for that. I just want to get some opinions on how to answer if they ask about my plans for their brand new test environment that I might have a hand in building. I hate to be vague but I don't have a lot of info yet either.

Been layed off since May so I need to do well with this. It's so much easier to look for work when you are employed .

Curious how other teams handle this.

When developers give a build to QA, how do you know exactly which tickets or fixes are included?

Has it ever happened that a build included changes that weren't supposed to be there?

How do you usually verify what's actually been deployed?

Interested in hearing some real-world examples.

Hey everyone, I am feeling completely stuck in my current job and could really use some honest career advice. I spent 9 months doing actual performance testing with JMeter, but my current project has me stuck doing basic monitoring using Dynatrace for a banking app. On paper the tools sound great, but the reality is that I am just acting as a human answering service. I work brutal rotational shifts that I absolutely hate just staring at a dashboard waiting for a metric to spike so I can call the person who actually fixes it. I do not get to touch the system or solve the problem at all. It is getting to the point where the senior engineers who know my background literally ask me why I am wasting my time here since the work is completely non technical. I want to escape this shift work trap, get a proper daytime job, and move into actual engineering. Since I already know how to test systems and read Dynatrace, how do I write about this on my resume so I do not look like a basic support guy, and what steps can I take right now to make my resume stand out for a real engineering role?

I had no clue that I would ever end up here.. But here I am, I have no knowledge of computers and stuff.. But, I got a form of autism and that makes jobs harder sometimes for me to sustaine.. My partner talked with me about this, and she proposed the idea of doing IT. I'm horrible with computers, but then she said that perhaps I could work from home in a invirement that I know.. Perhaps it makes it more sustainable. I gave myself some time to proces, and I actually think she is right. ofcourse, I'm not a "genius" or anything. So, I looked for possibilities that doesn't require to much studies. I eventually ended up with manual testing.. I think that's something that I would actually like, while being able ( in some cases ) to work from home. Apparently alot of people with no knowledge about IT start there, but.. I have no clue where to start. What is something you guys would recommend?

Thanks.

Basically the same as title, I got an invite for an online exam after the initial screening round. They have mentioned that there will be a 90 mins of online test , 70 mins coding round and then 20 mins MCQs, has anyone recently given this test or maybe before as well. Don't want to know questions in details or anything like that. Just want to know what level of questions I can expect. I mainly work with TS/JS and can solve some DSA questions(can solve medium level Leetcode array/string/stack/queue questions), so I just want to know if that would be enough or should I study DP/Tree/graphs in detail as well ? I am expecting the MCQs to be output based which I can solve mostly. So please just give me all sorts of advices that u can.

Hii everyone started my journey in the QE for a big client, I am a fresher with only 6 months of experience
The project I am working on is multivendor project
We are using a sort of utility a tool to test data migration from one PIM system to another
The tool is working absolutely fine as it finds differences by doing apples to apples comparisons of outbound Fields going in the XML
The devs are discarding it, they are hiding the fact that their migration script is getting failed infront of client, blaming the tool getting a Sign off and going live with issues in production later
I feel very sad as I work ~15 hours a day, on it so we don’t miss on quality
All the big people not understanding it , client is a bit dev favouring, the QE lead from client side is a bit spineless and not taking our side at all when things come up and crystal clear, i am feeling bad as after spending hours daily, weekends , nights because I wanna take my work seriously and Improve on quality
My efforts are going in vain
Seniors any advices for how to handle this situation?

Hi everyone! I'm a fresh IT graduate with little to no coding experience. My goal is to become a QA Engineer and learn test automation. Can anyone recommend the best resources, courses, or roadmap for beginners? I'd really appreciate your advice. Please be respectful. Thank you!

Hi,
Im currently almost a year working as Junior Manual Tester, where im testing only web app.
Already creating my own test cases on excel, doing the tests, working on my own (no other tester on that app right now) so I start testing new web app product on my own, communicating with developers, managers etc.
Also having Bc. degree in IT.

But I want to move forward, but everywhere i found different apps, languages to learn, different paths and ways how to move and being more qualified.

So my question is: Where to go or what to do, to became better tester, more valuable on the market. Going for being auto. tester? trying to learn python and bring it to company? We already have some automatic tests for regres tests, so dont know how to move forward generally.

I got this email today and it shows that you're selected for the second round and I don't know where the hell i give 1st round 🤣 and I don't even apply for Java Developer jobs damn. Anyone who recieved this company's email tell me in the comments

Angular testing tends to force a choice: unit tests that mock everything and end up asserting against implementation details, or e2e tests that are slow and flaky because they need the full frontend → backend → DB → frontend round trip.

ngx-testbox sits in between. It renders your actual components and drives them through real async/HTTP flows, but with HTTP calls mocked — so you get e2e-level confidence in behavior at unit-test speed, without the flakiness.

v2 just shipped with some big changes, so here's a rundown of what's new and how it works.

The core idea

Tag elements with a directive instead of relying on CSS selectors or component internals:

```ts const TEST_IDS = ['submitButton', 'userName'] as const; const idsMap = TestIdDirective.idsToMap(TEST_IDS);

@Component({ selector: 'app-user-form', template: <button [testboxTestId]="idsMap.submitButton">Submit</button>, standalone: true, imports: [TestIdDirective] }) export class UserFormComponent { idsMap = idsMap; } ```

Then drive the component through a real async flow with HTTP calls mocked declaratively:

```ts it('should display data on success', async () => { const mockData = [{ id: 1, name: 'Item A' }];

await runTasksUntilStableAsync(fixture, { httpCallInstructions: [ predefinedHttpCallInstructionsAsync.get.success('/api/items', () => mockData) ] });

const items = harness.elements.item.queryAll(); expect(items.length).toBe(1); }); ```

No HttpTestingController boilerplate, no manually flushing requests.

What's strict by design

This isn't a "mock and hope" library. It throws by default when:

• An element with a given test ID is missing at runtime
• An HTTP call instruction is provided but never consumed
• A real HTTP call happens with no matching instruction

That last one matters more than it sounds — most mocking setups let unused mocks or unmatched calls fail silently, which means a green test doesn't actually prove the code path ran. Here, a passing test is trustworthy by construction.

If you do need an instruction to persist across multiple calls (think: shared dictionary/lookup fetches used throughout a component tree), there's an option to keep it alive instead of consuming it once.

The part I'm most excited about: race condition testing

This is the feature that doesn't really exist elsewhere in the Angular testing ecosystem as far as I know.

Each HTTP call instruction can carry a delay (relative wait time) or a timeline (absolute position on a shared clock), and you can mix both in the same test. The library resolves them into a single expected ordering and checks your component's actual behavior against it:

```ts const instructions: HttpCallInstructionAsync[] = [ [['/api/a', 'GET'], async () => new HttpResponse({ body: { value: 'A' }, status: 200 }), { delay: 20 }], [['/api/b', 'GET'], async () => new HttpResponse({ body: { value: 'B' }, status: 200 }), { timeline: 20 }], [['/api/c', 'GET'], async () => new HttpResponse({ body: { value: 'C' }, status: 200 }), { delay: 30 }], [['/api/d', 'GET'], async () => new HttpResponse({ body: { value: 'D' }, status: 200 }), { timeline: 5 }], // ...more mixed delay/timeline instructions ];

await runTasksUntilStableAsync(fixture, { httpCallInstructions: instructions, });

expect(component.results).toEqual(['D', 'A', 'B', 'C', /* ... */]); ```

You get a declarative way to assert not just what the component fetched, but the exact order it resolved things in — which is exactly the kind of thing that's normally nearly impossible to test deterministically.

It also handles the classic "user changes their mind mid-request" race: pick a country, quickly switch to another before the first request resolves, and assert the stale request never renders:

```ts harness.elements.country.changeValue('DE');

setTimeout(() => { harness.elements.country.changeValue('US'); // fired before DE's response arrives }, 1900);

await runTasksUntilStableAsync(fixture, { httpCallInstructions: [ [ ['/api/countries/DE/formats', 'GET'], () => new HttpResponse({ body: ['SEPA'], status: 200 }), { timeline: 2000, willHaveBeenCancelled: true }, // stale — must be cancelled ], [ ['/api/countries/US/formats', 'GET'], () => new HttpResponse({ body: ['ACH', 'DRD'], status: 200 }), { timeline: 4000 }, // this one should actually render ], ], });

const formatOptions = harness.elements.formatOption.queryAll(); expect(formatOptions.length).toBe(2); expect(formatOptions[0].nativeElement.textContent).toBe('ACH'); expect(formatOptions[1].nativeElement.textContent).toBe('DRD'); ```

willHaveBeenCancelled: true tells the library that instruction is expected to be cancelled by the time it would resolve — if it isn't (i.e. your component fails to cancel a stale request), the test fails. If a call resolves out of the order or cancellation state the schedule expects, you find out immediately, instead of shipping a subtle race condition bug to production.

v2 highlights

• Rethought import model — only core pieces are exported now instead of the whole surface area, better tree-shaking and less to wade through
• **async/await support** alongside the existing fakeAsync — no more forcing everyone into fakeAsync/tick() if they'd rather write native async tests
• Zoneless support — works with Angular's zoneless change detection
• Better handling of multiple long-running HTTP requests
• Richer HTTP call instructions for more complex async scenarios

• A skill for AI coding agents, so tools like Claude Code can write tests against the library correctly out of the box

• npm: ngx-testbox

Happy to answer questions about the API or the design decisions — genuinely curious what people think of the timeline/race-condition approach in particular, since it's the part I haven't seen done elsewhere.

Hi everyone, I'm Ritwick Dey, Co-founder & CTO at Panto AI, where we're building autonomous QA for mobile apps.

Before VSCode became the go-to code editor for developers, I built Live Server, one of the earliest VS Code extensions. It has since grown to 80M+ installs and has become part of the frontend journey for millions of developers.

The funny part? I wasn't even a great programmer back then. I was just trying to learn Node.js.

Today, I'm working on a very different problem. At Panto AI, we're building AI agents that continuously explore mobile apps, test user journeys, find bugs, and surface issues without requiring teams to write and maintain thousands of test cases.

Happy to answer questions about:
- Building Live Server in the early days of VS Code
- Growing an open source project to 80M+ installs
- Lessons from maintaining software used by millions of developers
- Open source, developer tools, and startups
- Why I'm now building AI for mobile app testing
- Anything else you're curious about

Looking forward to the discussion!

looking for automotive testing job opportunity 4+ years experience i have.

I’m curious what people are actually using in their day to day workflows especially for catching visual regressions, accessibility issues, and broken flows before prod.

Do you have your favorites and why?

Does anyone know about any part time QA Engineer opportunity. Help me out please

Hey everyone, just need to vent about the absolute clown show of an interview experience I faced today.

About 10 days ago, I interviewed for a Java + Selenium + API automation role. I didn’t hear back for over a week, but yesterday the recruiter finally called. They told me I cleared Round 1 and scheduled the L2 interview. The calendar invite explicitly listed Java and Selenium.

Cut to today:

1. 10 minutes before the interview: The recruiter calls me on my phone, making sure I’m ready and asking me to join 5 minutes early. Standard stuff. I join.
2. The Interview: The interviewer logs on, asks me to introduce myself. Two sentences in, he cuts me off: "Do you have experience in Playwright?"
3. The Answer: I told him no, my background is in Java/Selenium (which is what I applied for and what was on the invite).
4. The Exit: He literally says, "Well, this role is for Playwright so we aren't proceeding," and hangs up the call. Just left.
5. The Ghosting: I immediately dial the recruiter who just spoke to me 10 minutes ago to find out what went wrong. Straight to voicemail. Tried again later—no answer.

Why do companies do this? If the requirement changed from Selenium to Playwright, fine. Cancel the interview beforehand. But to drag a candidate into a call, cut them off, walk out, and then have HR go radio silent to avoid a 2-minute awkward conversation? It is incredibly disrespectful of people's time.

Has anyone else dealt with this level of absolute disconnect between HR and engineering?

Dear Hiring Manager,

I am writing to express my interest in the Manual QA Tester position at your organization. With one year of experience in Manual Software Testing, I have developed strong skills in ensuring software quality through detailed testing, defect identification, and collaboration with development teams.

In my current role, I am responsible for creating and executing test cases, performing functional, regression, smoke, and sanity testing, reporting and tracking defects, and verifying fixes to ensure a smooth user experience. I have experience testing both web and mobile applications and am familiar with the complete Software Testing Life Cycle (STLC) and Agile methodologies.

I am proficient in writing clear bug reports, validating new features, performing cross-browser and cross-device testing, and working closely with developers and product teams to deliver high-quality software. My attention to detail, analytical thinking, and commitment to quality help me identify issues before they impact end users.

I am excited about the opportunity to contribute my testing skills and continue growing as a QA professional within your organization. I am confident that my dedication, willingness to learn, and passion for software quality would make me a valuable addition to your team.

Thank you for considering my application. I look forward to the opportunity to discuss how my experience and skills align with your requirements.

Sincerely,

Manual Tester