Tag Info

New answers tagged

0

Getting your 'feet wet' with QA Yeah, let's do that. Because every team wants to hire someone who doesn't want to be there? (Sarcasm not directed towards you) This is a growing pandemic in the QA world. As an SDET/Automation/QA I have to justify at every interview why I am still in QA and not a developer. The bottom line is that I LOVE my job. QA is fun! ...


0

As a beginner, you most importantly should have the desire to excel as a tester. You should be self motivated. You should be mad about testing. You should not feel discouraged with one or two (or more) failures in the beginning because you and only you can do this, nobody can drag or force you into it, if you start disliking it after say wetting your ...


0

I think that the answer is "Yes", load test should have checks for response validity. I.e. if you send bad username/password pair it is expected to get 401 or 403 HTTP response and JMeter shouldn't consider it as sampler failure. If response code is 200 but the response body doesn't contain "bla-bla" although shouldn't it also should indicate test failure. ...


0

I would say that some validation is almost always needed. For example I have tested website where if the login failed then all subsequent requests get a 200-OK response, but every response body requests a username and password. Adding a simple verification that the response to the login contains "login successful" or something equivalent detects the login ...


0

The simplest answer is if your customer is telling you to do this, you do it. If you don't provide what your customer wants, you run the risk of them telling you after you've developed the test that the results aren't valid because you've ignored their instructions. I've seen this happen: a very simple load test had to incorporate a lot of business logic ...



Top 50 recent answers are included