Post by account_disabled on Dec 7, 2023 3:08:54 GMT -5
A project manager an analyst additional developers and a test manager were hired. My first day and I remember it perfectly resembled the first day at my old company many years ago. And so the story comes full circle. I found the client's application without documentation assumptions requirements and I had to create a test plan testing strategies test cases etc. All I had to do was sit down and explore. I gave myself two full days. Purpose familiarization with the application. The test report contained several dozen errors and glitches along with screenshots.
On its basis JIRA tasks regarding errors were created and later test cases were designed. A big problem here was the lack of any requirements everything was done intuitively by developers. Exploratory testing in this situation not only helped me as a tester but also contributed to the development of the Email Marketing List application. We started discussing whether the application was user friendly and talking about ergonomics in the system. So the exploration tests served their purpose. Read also Why software testing is important Minimalist test case When time runs out. Exploratory testing can also be used at the end of the project when there are a lot of errors to fix.
New functionalities are added quickly which means that new versions are released almost every day and there is a need for ongoing testing including regression. Which tester doesn't know this? This is the moment when many managers or project managers think about limiting tests. Let's never allow this. This is a simple way to end the project in failure. Perhaps it is worth proposing exploration tests then. In the professional literature opinions are divided you will either encounter an absolute no when it comes to exploration when regression tests are being conducted or quite the opposite.
On its basis JIRA tasks regarding errors were created and later test cases were designed. A big problem here was the lack of any requirements everything was done intuitively by developers. Exploratory testing in this situation not only helped me as a tester but also contributed to the development of the Email Marketing List application. We started discussing whether the application was user friendly and talking about ergonomics in the system. So the exploration tests served their purpose. Read also Why software testing is important Minimalist test case When time runs out. Exploratory testing can also be used at the end of the project when there are a lot of errors to fix.
New functionalities are added quickly which means that new versions are released almost every day and there is a need for ongoing testing including regression. Which tester doesn't know this? This is the moment when many managers or project managers think about limiting tests. Let's never allow this. This is a simple way to end the project in failure. Perhaps it is worth proposing exploration tests then. In the professional literature opinions are divided you will either encounter an absolute no when it comes to exploration when regression tests are being conducted or quite the opposite.