How a Good Bug Hunter Prioritizes his Bug Hunting Activities in Software Testing

-
Let us firstly understand as to what is a bug hunter?

A bug hunter is an experienced & enthusiastic exploratory tester. Good bug hunters usually do the following:

1) Do initial exploratory testing of a suspect area, to develop ideas for more detailed attacks that can be performed by less experienced testers.

2) Explore an area that is allegedly low risk - can he quickly find bugs that would lead to reassessment of the risk?

3) Troubleshoot key areas that seem prone to irreproducible bugs.

4) Find critical bugs that will convince the project manager to slip a (premature) release date.

How to prioritize the bug hunting activities?

Generally the mission of a good bug hunter is finding bugs that are important (as opposed to insignificant) and finding them quickly. If so, what does this mean in terms of the tests that are run?

You can use following suggestions to prioritize bug hunting in your software testing effort.

1) Test things that are changed before things that are the same. Fixes and updates mean fresh risk.

2) Test core functions before contributing functions. Test the critical and the popular things that the product does. Test the functions that make the product what it is.

3) Test capability before reliability. Test whether each function can work at all before going deep into the examination of how any one function performs under many different conditions.

4) Test common situations before esoteric situations. Use popular data and scenarios of use.

5) Test common threats before exotic threats. Test with the most likely stress and error situations.

6) Test for high-impact problems before low-impact problems. Test the parts of the product that would do a lot of damage in case of failure.

7) Test the most wanted areas before areas not requested. Test any areas and for any problems that are of special interest to someone else on the team.

Conclusion: You will also find important problems sooner if you know more about the product, the software and hardware it must interact with, and the people who will use it. Study these thoroughly.

Comments

Post a Comment

Popular posts from this blog

Steps to Deploy the OFSAA application in WEBLOGIC server:

-
Steps to Deploy the OFSAA application in WEBLOGIC server: ========================================================= 1) Generate the "context_name.ear" from the FIC_WEB area by executing the ./ant.sh 2) Create a folder by the name "applications" within the domain directory 3) Create a folder by the name "context_name.ear" within the newly created "applications" folder 4) Copy the context_name.ear file from the FIC_WEB folder to the newly create the "context_name.ear" folder created within the applciations folder 5) Explode the .ear file copied from the FIC_WEB area (jar -xvf context_name.ear), There are 2 files and 1 directory created after the .ear file is exploded as mentioned below a) context_name.war ---> file b) context_name.ear ---> file c) META_INF ---> folder 6) Delete the above files (.ear and .war files) 7) Create a new folder by the name "context_name.war" 8) Copy the context_name.war file from th
Read more

Steps for OFSAA ALM cash flow generation

-
Please find the steps below for the OFSAA ALM cashflow generation. -------------------------------------------------------------------------------------------------------------- 0. OBJECT REGISTRATION 1. Create Product Hierarchy in front end.--- DIM_PRODUCTS_B 2. Create COA hierarchy in the front end. -- dim_common_coa_b 3. Map product members to COAs 4. Create one Legal Entity in the Front end. 5. Execute "Reverse Population" -- DT name : REVERSE_POPULATION 6. Create one Active Time bucket. 7. Populate DIM_DATE : Execute function "" in the back end with start date and end date. 8. Populate FSI_D_LOAN contracts 9. Create one product characteristic in ALM 10. Create one ALM Static Deterministic process for Loan data. 11. Execute from ALM Process. 12. Use the below queries for cashflow data. select /* + PARALLEL(16)*/ a.as_of_date, a.account_number, a.amrt_type_cd, a.int_type, a.origination_date, a.last_reprice_date, a.next_reprice_date, a.ma
Read more

Client / Server Applications

-
What is: The client–server characteristic describes the relationship of cooperating programs in an application. The server component provides a function or service to one or many clients, which initiate requests for such services. Advantages: * In most cases, a client–server architecture enables the roles and responsibilities of a computing system to be distributed among several independent computers that are known to each other only through a network. This creates an additional advantage to this architecture: greater ease of maintenance. For example, it is possible to replace, repair, upgrade, or even relocate a server while its clients remain both unaware and unaffected by that change. * All data is stored on the servers, which generally have far greater security controls than most clients. Servers can better control access and resources, to guarantee that only those clients with the appropriate permissions may access and change data. * Since data storage is centralized, update
Read more