Q. High severity, low priority bug?
A: — A page is not often accessed, or some activity is executed rarely but that thing outputs some essential Data wrongly, or corrupts the data, this will be a bug of H severity L priority
Q. If project wants to release in 3months what type of Risk analysis you do in Test plan?
A: – Use risk analysis to decide where testing should be focused. Since it’s not often possible to test every possible portion of an software/application, every probable combination of events, every dependency, or everything that could go wrong, risk analysis is suitable to most software development projects. This involve judgment skills, common sense, and experience.
Considerations can include:
• Which functionality is most chief to the project’s intended purpose?
• Which functionality is most visible to the user?
• Which functionality has the largest safety impact?
• Which functionality has the largest financial impact on users?
• Which aspects of the application are most important to the customer?
• Which aspects of the application can be tested early in the development cycle?
• Which parts of the code are most complex, and thus most subject to errors?
• Which parts of the application were developed in rush or panic mode?
• Which aspects of similar/related previous projects caused problems?
• Which aspects of similar/related previous projects had large maintenance expenses?
• Which parts of the requirements and design are unclear or poorly thought out?
• What do the developers think are the highest-risk aspects of the application?
• What kinds of problems would cause the worst publicity?
• What kinds of problems would cause the most customer service complaints?
• What kinds of tests could easily cover multiple functionalities?
• Which tests will have the best high-risk-coverage to time-required ratio
48. Test cases for IE 6.0 ?
A:– Test cases for IE 6.0 i.e Internet Explorer 6.0:—
1)First I go for the Installation part, means that –
Is it working with all versions of Windows ,Netscape or other software(s) in other words we can say that IE must check with all hardware and software parts.
2) Secondly go for the Text Part means that all the Text part appears in regular and smooth manner.
3) Thirdly go for the Images Part means that all the Images come into view in regular and smooth manner.
4) URL must run in a better way.
5) Suppose Some other language used on it then URL take the Other Characters, Other than Normal Characters.
6)Is it working with Cookies frequently or not.
7) Is it in relation to with different script like JScript and VBScript.
8)HTML Code work on that or not.
9) Troubleshooting works or not.
10) All the Tool bars are work with it or not.
11) If Page has Some Links, than how much is the Max and Min Limit for that.
12) Test for Installing Internet Explorer 6 with Norton Protected Recycle Bin enabled.
13) Is it working with the Un-installation Process?
14) Last but not the least test for the Security System for the IE 6.0
Q. Where you involve in testing life cycle, what type of test you perform?
A:– Normally test engineers concerned from entire test life cycle i.e, test plan, test case preparation, execution, reporting. Generally system testing, regression testing, adhoc testing etc.
Q. What is Testing environment in your company, means how testing process start?
A:– testing process is going as follows
Quality assurance unit
Quality assurance manager
Test lead
Test engineer
Q. Who prepares the use cases?
A:– In Any company apart from the small company Business analyst prepares the use cases. But in small company Business analyst prepares along with team lead.
Q. What methods have you used to develop test cases?
A:– Usually test engineers uses 4 types of methodologies
1. Boundary value analysis
2.Equivalence partition
3.Error guessing
4.Cause effect graphing
Q. Why we call it as a regression test nor retest?
A:– If we test whether defect is closed or not i.e Retesting But here we are checking the impact also regression means repeated times
54. Is automated testing better than manual testing. If so, why?
A:– Automated testing and manual testing have there own advantages as well as disadvantages
Advantages: It boost the efficiency of testing process speed in process
reliable
Flexible
Disadvantage’s
Tools should have compatibility with our development or deployment tools need lot of time at first If the necessities are changing endlessly then Automation is not suitable
Manual: If the requirements are changing endlessly Manual is suitable Once the build is stable with manual testing then only we go 4 automation
Disadvantages:
Time Consuming
We can not do some type of testing manually
E.g Performances
Q. What is the exact difference between a product and a project? Give an example?
A:– Project Developed for specific client necessities are defined by client. Product developed for market necessities are defined by company itself by conducting market survey
Example
Project: the shirt which we are interested stitching with tailor as per our specifications is project
Product: Example is “Ready made Shirt” where the particular company will imagine particular measurements they made the product
Mainframes is a product
Product has many mo of versions
but project has fewer versions i.e depends upon change request and enhancements
Q. Define Brain Storming and Cause Effect Graphing? With example.
A: – Brain Storming:
A learning technique involving open group discussion intended to expand the range of available ideas.
OR
A meeting to generate creative ideas. At PEPSI Advertising, daily, weekly and bi-monthly brainstorming sessions are held by various work groups within the firm. Our monthly I-
Power brainstorming meeting is attended by the entire agency staff.
OR
Brainstorming is a highly planned process to help make ideas. It is based on the principle that you cannot generate and calculate ideas at the same time. To use brainstorming, you must first gain agreement from the group to try brainstorming for a fixed interval (eg six minutes).
CEG :
A testing technique that aids in selecting, in a systematic way, a high-yield set of test cases that logically relates causes to effects to produce test cases. It has a beneficial side effect in pointing out incompleteness and ambiguities in specifications.
Q. Actually by using severity u should know which one u need to solve so what is the need of priority?
A:– I guess severity replicate the seriousness of the bug where as priority refers to which bug should rectify first. of course if the severity is high the same case is with priority in normal.
Severity decided by the tester where as priority decided by developers. Which one need to answer first knows through priority not with severity. How serious of the bug knows through severity.
Severity is nothing collision of that bug on the application. Priority is nothing but weight to resolve the bug yeah of course by looking severity we can judge but sometimes high severity bug doesn’t have high priority At the same time High priority bug don’t have high severity. So we need both severity and priority
Q. What do u do if the bug that you bring into being is not accepted by the developer and he is saying its not reproducible. Note: The developer is in the on site location ?
A:– once again we will check that condition with all causes. Then we will attach screen shots with strong reasons. Then we will clarify to the project manager and also clarify to the client when they contact us
Sometimes bug is not reproducible it is because of different environment suppose development team using other environment and you are using different environment at this situation there is chance of bug not reproducing. At this situation please check the environment in the base line documents that is functional documents if the environment which we r using is correct we will raise it as defect We will take screen shots and sends them with test procedure also.
Q. What is the difference between three tier and two tier application?
A:– Client server is a 2-tier application. In this, front end or client is connected to
‘Data base server’ through ‘Data Source Name, front end is the monitoring level.
Web based architecture is a 3-tier application. In this, browser is connected to web server through TCP/IP and web server is connected to Data base server, browser is the monitoring level. In general, Black box testers are concentrating on monitoring level of any type of application.
All the client server applications are 2 tier architectures.
Here in these architecture, all the “Business Logic” is stored in clients and “Data” is stored in Servers. So if user request anything, business logic will b performed at client, and the data is retrieved from Server(DB Server). Here the problem is, if any business logic changes, then we
need to change the logic at each any every client. The best ex: is take a super market, i have branches in the city. At each branch i have clients, so business logic is stored in clients, but the actual data is store in servers.If assume i want to give some discount on some items, so i
need to change the business logic. For this i need to goto each branch and need to change the business logic at each client. This the disadvantage of Client/Server architecture.
So 3-tier architecture came into picture:
Here Business Logic is stored in one Server, and all the clients are dumb terminals. If user requests anything the request first sent to server, the server will bring the data from DB Sever and send it to clients. This is the flow for 3-tier architecture.
Assume for the above. Ex. if i want to give some discount, all my business logic is there in Server. So i need to change at one place, not at each client. This is the main advantage of 3-tier architecture.
