Post by account_disabled on Dec 7, 2023 3:09:17 GMT -5
Much time has passed exploratory tests have become more important they have been formalized and described in professional literature. When is it worth thinking about exploration? According to the International Software Testing Qualifications Board's dictionary specifically James Bach exploratory testing is An informal test design technique in which a tester designs tests as they are executed and uses information acquired during testing to design new and better tests.
While arguing with ISTQB for me a more important factor is learning about the application especially if we do not have documentation. Exploratory tests and conversations with developers and project participants allow you to get to know each system quite quickly. By Email Marketing List definition we do not need any documentation for exploratory testing. In turn you need a goal and a specific time frame. So when is it worth thinking about exploration? The tester's first meeting with the application We start working on a new project completely green hoping to work with documentation and be able to quickly gain knowledge. However it often happens that there is no documentation.
However there is often some fragmentary information in the form of text most often out of date and the rest is locked in the developers' heads. This was the situation I had to face in my first project it was a project for cash registers which in addition to sales were supposed to be able to charge mobile phones accept parcels etc. I would like to add that the company for which the project was prepared was one of the companies great organization. It included two giants when it comes to cash registers on the Polish market. The project was just being revived once again. The work on it so far has been as follows functionalities were added and further work was abandoned. What has already been created is the customer panel products for cash registers were about to be created.
While arguing with ISTQB for me a more important factor is learning about the application especially if we do not have documentation. Exploratory tests and conversations with developers and project participants allow you to get to know each system quite quickly. By Email Marketing List definition we do not need any documentation for exploratory testing. In turn you need a goal and a specific time frame. So when is it worth thinking about exploration? The tester's first meeting with the application We start working on a new project completely green hoping to work with documentation and be able to quickly gain knowledge. However it often happens that there is no documentation.
However there is often some fragmentary information in the form of text most often out of date and the rest is locked in the developers' heads. This was the situation I had to face in my first project it was a project for cash registers which in addition to sales were supposed to be able to charge mobile phones accept parcels etc. I would like to add that the company for which the project was prepared was one of the companies great organization. It included two giants when it comes to cash registers on the Polish market. The project was just being revived once again. The work on it so far has been as follows functionalities were added and further work was abandoned. What has already been created is the customer panel products for cash registers were about to be created.