There is also one relative methodology that is called Bug Hunting. In practice, this event is quite interesting and emotional.
Depending on the project, developed functionality and the number of developers in the team, the given event may be performed on the following scenario:
- Participation of all project team members (programmers, testers, managers, etc.).
- Creation of teams, where each one has members of different professions.
- Each team has to validate a particular program functionality (interface, data storage, data processing, data transferring, performance and so on).
- There are deadlines for defect detection (4 hours, 8 working hours and so on).
- All the team members start validating one's functionality together.
- All the defects or wishes on improving the functionality are recorded.
- Detected defects are described in details if it’s needed.
- Each team represents all the detected defects on the general meeting.
- Defects from each team are shared in the document.
When the event is finished, all the documentation with detected bugs is passed to the testers, who reproduce them & introduce relevant defects in the bug tracking system.
There are some positive moments in the following type of team bug hunting:
- The involvement of the entire team;
- "A fresh perspective" on the product;
innovative approaches to verification;
- Developers often confess about the defects, which they haven’t seen in the code, but none of them shared this information.
If you are looking for more interesting and useful information about software testing services, different techniques and methods - click here & visit our official website.
Posts
1 comment:
In my context a Trojan horse hunt is because the identify suggests, a hunt (or search) for bugs. It is important to note that this used to be not the only process to trying out this product neither is it a silver bullet / seize all / safeguard website. This endeavor used to be a part of certainly one of our checking out missions which was once to furnish expertise to the product managers to support them make a release determination, they were concerned about finding as many bugs as possible in a brief space of time so that they would be prioritized and addressed if required.
Post a Comment