Manual Testing

  Home  Testing  Manual Testing


“Manual Testing Interview Questions and Answers will guide that Manual Testing is the process of manually testing software for defects. It requires a tester to play the role of an end user, and use most of all features of the application to ensure correct behavior. To ensure completeness of testing, the tester often follows a written test plan that leads them through a set of important test cases. So learn more about Manual Testing with this Manual Testing Interview Questions with Answers guide”



48 Manual Testing Questions And Answers

21⟩ What are the main bugs which were identified by you and in that how many are considered as real bugs?

If you take one screen, let's say, it has got 50 Test conditions, out of which, I have identified 5 defects which are failed. I should give the description defect, severity and defect classfication. All the defects will be considered.

Defect Classification are:

GRP : Graphical Representation

LOG : Logical Error

DSN : Design Error

STD : Standard Error

TST : Wrong Test case

TYP : Typographical Error (Cosmotic Error)

 158 views

22⟩ What is Six sigma?

Six Sigma:

A quality discipline that focuses on product and service excellence to create a culture that demands perfection on target, every time.

Six Sigma quality levels

Produces 99.9997% accuracy, with only 3.4 defects per million opportunities.

Six Sigma is designed to dramatically upgrade a company's performance, improving quality and productivity. Using existing products, processes, and service standards,

They go for Six Sigma MAIC methodology to upgrade performance.

MAIC is defined as follows:

Measure: Gather the right data to accurately assess a problem.

Analyze: Use statistical tools to correctly identify the root causes of a problem

Improve: Correct the problem (not the symptom).

Control: Put a plan in place to make sure problems stay fixed and sustain the gains.

Key Roles and Responsibilities:

The key roles in all Six Sigma efforts are as follows:

Sponsor: Business executive leading the organization.

Champion: Responsible for Six Sigma strategy, deployment, and vision.

Process Owner: Owner of the process, product, or service being improved responsible for long-term sustainable gains.

Master Black Belts: Coach black belts expert in all statistical tools.

Black Belts: Work on 3 to 5 $250,000-per-year projects; create $1 million per year in value.

Green Belts: Work with black belt on projects.

 170 views

23⟩ What are cookies? Tell me the advantage and disadvantage of cookies?

Cookies are messages that web servers pass to your web browser when you visit Internet sites. Your browser stores each message in a small file. When you request another page from the server, your browser sends the cookie back to the server. These files typically contain information about your visit to the web page, as well as any information you've volunteered, such as your name and interests. Cookies are most commonly used to track web site activity. When you visit some sites, the server gives you a cookie that acts as your identification card. Upon each return visit to that site, your browser passes that cookie back to the server. In this way, a web server can gather information about which web pages are used the most, and which pages are gathering the most repeat hits. Only the web site that creates the cookie can read it. Additionally, web servers can only use information that you provide or choices that you make while visiting the web site as content in cookies. Accepting a cookie does not give a server access to your computer or any of your personal information. Servers can only read cookies that they have set, so other servers do not have access to your information. Also, it is not possible to execute code from a cookie, and not possible to use a cookie to deliver a virus.

 137 views

24⟩ What is stub? Explain in testing point of view?

Stub is a dummy program or component, the code is not ready for testing, it's used for testing...that means, in a project if there are 4 modules and last is remaining and there is no time then we will use dummy program to complete that fourth module and we will run whole 4 modules also. The dummy program is also known as stub.

 141 views

25⟩ Define Brain Stromming and Cause Effect Graphing?

BS:

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 structured process to help generate ideas. It is based on the principle that you cannot generate and evaluate 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.

 132 views

26⟩ Password is having 6 digit alphanumeric then what are the possible input conditions?

Including special characters also Possible input conditions are:

1) Input password as = 6abcde (ie number first)

2) Input password as = abcde8 (ie character first)

3) Input password as = 123456 (all numbers)

4) Input password as = abcdef (all characters)

5) Input password less than 6 digit

6) Input password greater than 6 digits

7) Input password as special characters

8) Input password in CAPITAL ie uppercase

9) Input password including space

10) (SPACE) followed by alphabets /numerical /alphanumerical/

 143 views

27⟩ Explain agile testing?

Agile testing is used whenever customer requirements are changing dynamically

If we have no SRS, BRS but we have test cases does you execute the test cases blindly or do you follow any other process.

Test case would have detail steps of what the application is supposed to do.

1) Functionality of application.

2) In addition you can refer to Backend, is mean look into the Database. To gain more knowledge of the application.

 132 views

29⟩ Verification and validation?

Verification is static. No code is executed. Say, analysis of requirements etc.

Validation is dynamic. Code is executed with scenarios present in test cases.

 131 views

31⟩ What is mean by release notes?

It's a document released along with the product which explains about the product. It also contains about the bugs that are in deferred status.

 241 views

32⟩ Give an example of high priority and low severity, low priority and high severity?

Severity level:

The degree of impact the issue or problem has on the project. Severity 1 usually means the highest level requiring immediate attention. Severity 5 usually represents a documentation defect of minimal impact.

Severity is levels:

* Critical: the software will not run

* High: unexpected fatal errors (includes crashes and data corruption)

* Medium: a feature is malfunctioning

* Low: a cosmetic issue

Severity levels

1. Bug causes system crash or data loss.

2. Bug causes major functionality or other severe problems; product crashes in obscure cases.

3. Bug causes minor functionality problems, may affect "fit anf finish".

4. Bug contains typos, unclear wording or error messages in low visibility fields.

Severity levels

* High: A major issue where a large piece of functionality or major system component is completely broken. There is no workaround and testing cannot continue.

* Medium: A major issue where a large piece of functionality or major system component is not working properly. There is a workaround, however, and testing can continue.

* Low: A minor issue that imposes some loss of functionality, but for which there is an acceptable and easily reproducible workaround. Testing can proceed without interruption.

Severity and Priority

Priority is Relative: the priority might change over time. Perhaps a bug initially deemed P1 becomes rated as P2 or even a P3 as the schedule draws closer to the release and as the test team finds even more heinous errors. Priority is a subjective evaluation of how important an issue is, given other tasks in the queue and the current schedule. It’s relative. It shifts over time. And it’s a business decision.

Severity is an absolute: it’s an assessment of the impact of the bug without regard to other work in the queue or the current schedule. The only reason severity should change is if we have new information that causes us to re-evaluate our assessment. If it was a high severity issue when I entered it, it’s still a high severity issue when it’s deferred to the next release. The severity hasn’t changed just because we’ve run out of time. The priority changed.

Severity Levels can be defined as follow:

S1 - Urgent/Showstopper. Like system crash or error message forcing to close the window.

Tester's ability to operate the system either totally (System Down), or almost totally, affected. A major area of the users system is affected by the incident and it is significant to business processes.

S2 - Medium/Workaround. Exist like when a problem is required in the specs but tester can go on with testing. Incident affects an area of functionality but there is a work-around which negates impact to business process. This is a problem that:

a) Affects a more isolated piece of functionality.

b) Occurs only at certain boundary conditions.

c) Has a workaround (where "don't do that" might be an acceptable answer to the user).

d) Occurs only at one or two customers. or is intermittent

S3 - Low. This is for minor problems, such as failures at extreme boundary conditions that are unlikely to occur in normal use, or minor errors in

layout/formatting. Problems do not impact use of the product in any substantive way. These are incidents that are cosmetic in nature and of no or very low impact to business processes.

 151 views

33⟩ Diff. between STLC and SDLC?

STLC is software test life cycle it starts with

* Preparing the test strategy.

* Preparing the test plan.

* Creating the test environment.

* Writing the test cases.

* Creating test scripts.

* Executing the test scripts.

* Analyzing the results and reporting the bugs.

* Doing regression testing.

* Test exiting.

SDLC is software or system development life cycle, phases are...

* Project initiation.

* Requirement gathering and documenting.

* Designing.

* Coding and unit testing.

* Integration testing.

* System testing.

* Installation and acceptance testing. " Support or maintenance.

 134 views

34⟩ What is Test Data Collection?

Test data is the collection of input data taken for testing the application. Various types and size of input data will be taken for testing the applications. Sometimes in critical application the test data collection will be given by the client also.

 124 views

35⟩ What are non-functional requirements?

The non-functional requirements of a software product are: reliability, usability, efficiency, delivery time, software development environment, security requirements, standards to be followed etc.

 133 views

36⟩ Why we perform stress-testing, resolution-testing and cross- browser testing?

Stress Testing: - We need to check the performance of the application.

Def: Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements

Resolution Testing: - Some times developer created only for 1024 resolution, the same page displayed a horizontal scroll bar in 800 x 600 resolutions. No body can like the horizontal scroll appears in the screen. That is reason to test the Resolution testing.

Cross-browser Testing: - This testing some times called compatibility testing. When we develop the pages in IE compatible, the same page is not working in Fairfox or Netscape properly, because

most of the scripts are not supporting to other than IE. So that we need to test the cross-browser Testing

 148 views

37⟩ What is the minimum criteria for white box?

We should know the logic, code and the structure of the program or function. Internal knowledge of the application how the system works what's the logic behind it and structure how it should react to particular action.

 143 views

39⟩ What are the main key components in Web applications and client and Server applications? (differences)?

For Web Applications: Web application can be implemented using any kind of technology like Java, .NET, VB, ASP, CGI& PERL. Based on the technology,We can derive the components.

Let's take Java Web Application. It can be implemented in 3 tier architecture. Presentation tier (jsp, html, dthml,servlets, struts). Busienss Tier (Java Beans, EJB, JMS) Data Tier(Databases like Oracle, SQL Server etc., )

If you take .NET Application, Presentation (ASP, HTML, DHTML), Business Tier (DLL) & Data Tier ( Database like Oracle, SQL Server etc.,)

Client Server Applications: It will have only 2 tiers. One is Presentation (Java, Swing) and Data Tier (Oracle, SQL Server). If it is client Server architecture, the entire application has to be installed on the client machine. When ever you do any changes in your code, Again, It has to be installed on all the client machines. Where as in Web Applications, Core Application will reside on the server and client can be thin Client(browser). Whatever the changes you do, you have to install the application in the server. NO need to worry about the clients. Because, You will not install any thing on the client machine.

 145 views

40⟩ What is the formal technical review?

Technical review should be done by the team of members. The document, which is going to be reviewed, who has prepared and reviewers should sit together and do the review of that document. It is called Peer Review. If it is a technical document, It can be called as formal Technical review, I guess. It varies depends on the company policy.

 114 views