19

Take a deep breath step back and look at the big picture Talk to folks / your boss about standards. Have a meeting. Agree on standards including items such as special characters. Take short term initiatives this month to reduce long-term repetitive pain next year. and allow for humans I've lost track of the number of times I've: typed weird characters ...


15

When a new project development starts in an organization when does the testing role come in? It depends. It depends on the company, industry, development approach, etc. Two commonly referred to methods for development are Waterfall and Agile In Waterfall you do the testing once the development of a feature is done. In Agile you do the testing before* and ...


13

One of the Context-Driven Testing principles is: The product is a solution. If the problem isn’t solved, the product doesn’t work. Another way to say this is that software should work for its user, not for some generic/arbitrary/commonly-used set of definitions of how things should be. When he says Even if someone gives, the error message is ...


9

Unlike a monolithic application where you have a single point of test (more or less) in microservice you will have to test each service separately. I would suggest to consider the following points when you plan microservices-based app: Test automation. There will be pretty challenging to test microservice-app manually since the number of services is usually ...


9

This depends on what kind of limitations you are experiencing. You can come up with virtualization. This will let you run several environments in a single host.You can also approach with containerization where you use the same host but isolate your instances with effective segregation of computational resources. Both of these options require some non-trivial ...


8

I'm always on the lookout for grammar and spelling errors - purely because we're here to assure quality, and typo's aren't professional. It's usually not the developer's fault because they just copy + paste it from a requirements document or something similar, and testers are more likely to catch it. As a consumer - if a company can't spell properly, I won'...


7

If your current Agile practices and approaches are: Some projects are Agile where continuous feedback from client will be coming, and the developers need to work on the existing item if it's in testing phase too because the deadline of a project will be too short and the client won't extend the deadline. Then you are not agile Although Agile does ...


7

It really comes down to who is consuming the information contained in your notes and what that information will be used for. If your testing found a bug, for example, you would likely want to write up steps to reproduce, information about your environment, and other information that would help find and fix the bug. If you are reporting on what you tested to ...


7

Start with understanding what works: What data is valid ? What data is used ? What is successful ? What are the variations ? What are the users like ? What are the long term business goals ? What are the short term business goals ? Goals can be very different across industry, company stage, location, profit vs non-profit, etc. Learn what quality means to ...


6

I lean toward involving Test from the beginning. When building something, if you don't support ways of testing it from the beginning, you end up having to rip it up and add that later. This hurts the company. Let's discuss "testing". As a developer, I consider test to be essential feedback, many kinds of tests to be important, and the Test department ...


6

Testers have a role in every phase of a project (be it waterfall, iterative, or full on agile): Project planning - ensuring proper consideration is given to procuring and setting up of test architecture, and for both testing and resolving faults found during testing. Requirements gathering/setting - testers can help ensure the requirements are described and ...


6

Feeling guilty doesn't help your company ship higher-quality software. Instead of feeling guilty, use those escaped defects as signals about what you could learn next. It sounds like it would help to find a mentor: either a more experienced QA engineer or even a sympathetic developer or manager. If you can't find a mentor at work, you might try looking ...


6

I never heard of any formal artifact of that name but if you go with a simple test report I imagine you should be fine. Just write down what (exactly) was tested, where you tested what you found, what your passing criteria were and identify remaining risks. If they need anything else they'll tell you, or even better, just ask them beforehand. Being a good ...


6

Mindmap all the high-level features of the application together with business owners. Go over the map with stakeholders (e.g users, developers, managers, and sponsors). Do a risk assessment with some key people, maybe also analyze brittle areas based on defect reports. Write automated happy-path tests for the highest risk features first. Create a test-...


5

I would be curious to learn: How does one formulates test strategy for an given complex business critical application supporting multiple platforms and consists of complex technology layers ? Also in his strategy where and how does he employs automation wisely . As automation solutions can be designed on multiple levels and in numerous ways using different ...


5

There are some qualities a QA Lead/manager should possess like Determining, negotiating and agreeing on in-house quality procedures Knowledge of standards and specifications Customer requirements Investigating and setting standards Ensuring processes Operating staff Writing management and technical reports Manage Client Analyzing ...


5

Guilt comes easy. The only thing to do is learn from your mistakes. There are a few things to do whenever a bug slips past: Figure out when it was introduced. Some bugs may have been in the system long before they were found. Create a regression test so it doesn't slip by in the future. Figure out how it slipped by. This one can be a bit tricky. Sometimes ...


5

If I understand the situation correctly, then either (1) you're promoting the test code into master before the production code, or (2) your regression test suite includes tests that are not yet in master. If 1, change your promotion process so that test code and production code are always promoted together. If 2, change your regression test process to run ...


5

Just be yourself. They asked you to the final round, so they see potential in you. Swamping yourself with more topics and information might overwhelm you more than it benefits. The interviewers will look at you someone with 2 years of experience, not a guru/expert/god/know-it-all. Be honest, and saying I don't know is an good option to most questions. I ...


5

Should we take notes in a simple text file or should we take it in a fancy Excel sheet? I am used to carrying a notebook with me, It's my childhood practice. I believe as a human being I can't remember every point, I discussed with the teammates. I have all the things with me like a personal digital assistant, laptop, desktop, Personal Server, Personal ...


5

Automation Feasibility What is the timeframe ? What is the cost of failure ? How fast are development cycles ? What current testing is highly repetitive ? How quickly do we need to get feedback ? How complex is the process being tested ? Who is available with the necessary skills ? How much do automation developers cost ? What is the desired shape of our ...


4

In my experience this tension is fairly typical in every organization I work in. My advice: Criticism is often not received well so I focus more on improvement suggestions Consider a 1:1 with the person concerned to go over your concerns in more detail Use analogies like Oil Changes, Investments, Plants, Gardens to refer to the investment of time and ...


4

In my experience no tester likes to miss bugs. That said, it's impossible to test everything, so some bugs will escape to UAT and/or production. Our goal is to catch as many of the biggest risk bugs as we can. My suggestion would be to analyze any bug that's found in UAT or production. You're looking for how many customers/users would be impacted by the ...


4

Directly answering your question: NO,(serious) defects found after the release are not the fault of the tester alone! Any company thinking that way is a company I would leave ASAP. Having said that: improving your testing and sharing what has been tested and what has not been tested is a first step in communicating what actually has been done when testing. ...


4

For an API, I would consider this a bug. An application is possibly going to be parsing the text so it should be the same for any invalid project name. However, as a backend developer myself, it's definitely possible that it just isn't important enough to fix, compared to other issues. I think your main problem is not a technical one but the fact that you'...


3

Well, according to classical approach you should consider the costs of automated tests implementation as the investments and thus choose the tests whose automation would give you the maximum ROI. The challenge here is to calculate NetProfit value since this depends on your particular project specific and what you actually need to minimize (either the cost ...


3

Automation is on ongoing process, it never stops and it can always be improved. You should first prioritize the test cases, and then start automating from the most important ones. Focus on the functional cases first. For example, you should first automate a basic flow, smoke test, happy flow etc. After all the important test cases are automated and the ...


3

"May I watch you work, and ask questions about what you're doing?"


3

Why do you feel guilt? If you compare that one defect to the tens or hundreds of defects you did identify, is it really significant in the bigger picture? This is precisely why SQA is undervalued. You missed one defect, you caught hundreds - yet that one defect is what defines the perceived "value" of doing testing. Now it's a little different if lots of ...


3

The bug leakage will happen some times. Because of this,you should not deviate from your work and take further proactive actions. From the issue, you can treat as a learning and add the scenario in your existing test cases. When going thro the user scenario (UAT/Production issue), you can create combination of scenarios to prevent this. With this learning,...


Only top voted, non community-wiki answers of a minimum length are eligible