Basics about Manual Testing & Interview Questions

Basics about Manual Testing & Interview Questions

Unknown   February 28, 2014   Comment  

Here We are Providing Information about what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics.

Manual Testing Basics & Interview Questions


1 . What is diff. between CMMI and CMM levels?

Ans:  CMM: - this is applicable only for software industry. KPAs -18

CMMI: - This is applicable for software, out sourcing and all other industries. KPA - 25

2. What is the scalability testing?

Ans :

1. Scalability is nothing but how many users that the application should handle

2. Scalability is nothing but maximum no of users that the system can handle

3. Scalability testing is a subtype of performance test where performance requirements for response time, throughput, and/or utilization are tested as load on the SUT is increased over time.

4. As a part of scalability testing we test the expandability of the application. In scalability we test 1.Applicaation scalability, 2.Performance scalability

Application scalability: to test the possibility of implementing new features in the system or updating the existing features of the system. With the help of design doc we do this testing

Performance scalability: To test how the s/w perform when it is subjected to varying loads to measure and to evaluate the

Performance behavior and the ability for the s/w to continue to function properly under different workloads.

–> To check the comfort level of an application in terms of user load. And user experience and system tolerance levels

–> The point within an application that when subjected to increasing workload begin to degrade in terms of end user experience and system tolerance

–> Response time

Execution time

System resource utilization

Network delays

 stress testingè

3. What is status of defect when you are performing regression testing?

Ans: Fixed Status

4. What is the first test in software testing process?

A) Monkey testing

B) Unit Testing

c) Static analysis

d) None of the above

Ans:  Unit testing is the first test in testing process, though it is done by developers after the completion of 

coding it is correct one.

5. When will the testing starts? a) Once the requirements are Complete b) In requirement phase?

Ans:- Once the requirements are complete.

This is Static testing. Here, u r supposed to read the documents (requirements) and it is quite a common issue in S/w industry that many requirements contradict with other requirements. These are also can be reported as bugs. However, they will be reviewed before reporting them as bugs (defects).

6. What is the part of Qa and QC in refinement v model?

Ans: V model is a kind of SDLC. QC (Quality Control) team tests the developed product for quality. It deals only with product, both in static and dynamic testing. QA (Quality Assurance) team works on the process and manages for better quality in the process. It deals with (reviews) everything right from collecting requirements to delivery.

7. What are the bugs we cannot find in black box?

Ans:  If there r any bugs in security settings of the pages or any other internal mistake made in coding cannot be found in black box testing.

8. What are Microsoft 6 rules?

Ans: As far as my knowledge these rules are used at user Interface test.

These are also called Microsoft windows standards. They are

. GUI objects are aligned in windows

• All defined text is visible on a GUI object

• Labels on GUI objects are capitalized

• Each label includes an underlined letter (mnemonics)

• Each window includes an OK button, a Cancel button, and a System menu

9. What are the steps to test any software through automation tools?

Ans: First, you need to segregate the test cases that can be automated. Then, prepare test data as per the requirements of those test cases. Write reusable functions which are used frequently in those test cases. Now, prepare the test scripts using those reusable functions and by applying loops and conditions where ever necessary. However, Automation framework that is followed in the organization should strictly follow throughout the process.

10. What is Defect removable efficiency?

Ans: The DRE is the percentage of defects that have been removed

During an activity, computed with the equation below. The DRE can also be computed for each software development activity and plotted on a bar graph to show the relative defect removal efficiencies for each activity. Or, the DRE may be computed for a specific task or technique (e.g. design inspection, code walkthrough, unit test, 6 month operation, etc.) Number Defects Removed

DRE = –—————————————————— * 100

Number Defects at Start of Process

DRE=A/A+B = 0.8

A = Testing Team (Defects by testing team)

B = customer ( ” ” customer )

If dre <=0.8 then good product otherwise not.

Qn. Example for bug not reproducible?

A: — Difference in environment.

11. Difference between adhoc testing and error guessing?

Ans: Adhoc testing: without test data r any documents performing testing.

Error Guessing: This is a Test data selection technique. The selection criterion is to pick values that seem likely to cause errors.

12. Diff between test plan and test strategy?

Ans: Test plan: After completion of SRS learning and business requirement gathering test management concentrate on test planning, this is done by Test lead, or Project lead.Test Strategy: Depends on corresponding testing policy quality analyst finalizes test Responsibility Matrix. This is dont by QA. But both  Documents.

13. What is “V-n-V” Model? Why is it called as “V”& why not “U”? Also tell at what Stage Testing should be best to stared?

Ans:It is called V coz it looks like V. the detailed V model is shown below.

SRS                          Acceptance testing

     \                         /

      \                       /

    HLD (High Level Design)   System testing

       \                    /

        \                  /

       LLD (Low level      Integration testing

             Design)     /

          \              /    

           \            Unit Testing

            \          /

             \        /

               Coding

There is no such stage for which you wait to start testing.

Testing starts as soon as SRS document is ready. You can raise defects that are present in the document. It’s called verification.

14. What is difference in between Operating System 2000 and OS XP?

Ans: Windows 2000 and Windows XP are essentially the same operating system (known internally as Windows NT 5.0 and Windows NT 5.1, respectively.) Here are some considerations if you’re trying to decide which version to use:

Windows 2000 benefits:

1) Windows 2000 has lower system requirements, and has a simpler interface (no “Styles” to mess with).

2) Windows 2000 is slightly less expensive, and has no product activation.

3) Windows 2000 has been out for a while, and most of the common problems and security holes have been uncovered and fixed.

4) Third-party software and hardware products that aren’t yet XP-compatible may be compatible with Windows 2000; check the manufacturers of your devices and applications for XP support before you upgrade.

Windows XP benefits:

1) Windows XP is somewhat faster than Windows 2000, assuming you have a fast processor and tons of memory (although it will run fine with a 300 MHz Pentium II and 128MB of RAM).

2) The new Windows XP interface is more cheerful and colorful than earlier versions, although the less- cartoon “Classic” interface can still be used if desired.

3 Windows XP has more bells and whistles, such as the Windows Movie Maker, built-in CD writer support, the Internet Connection Firewall, and Remote Desktop Connection.

4) Windows XP has better support for games and comes with more games than Windows 2000.

5) Manufacturers of existing hardware and software products are more likely to add Windows XP compatibility now than Windows 2000 compatibility.

15. What is bug life cycle?

Ans: New: when tester reports a defect

Open: when developer accepts that it is a bug or if the developer rejects the defect, then the status is turned into “Rejected”

Fixed: when developer make changes to the code to rectify the bug…

Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned into “Closed” and if the problem resists again, it’s “Reopen

16. What is deferred status in defect life cycle?

Ans: Deferred status means the developer accepted the bus, but it is scheduled to rectify in the next build

17. What is smoke test?

Ans: Testing the application whether it’s performing its basic functionality properly or not, so that the test team can go ahead with the application

18. Do you use any automation tool for smoke testing?

Ans:- Definitely can use.

20. What is Verification and validation?

Ans: Verification is static. No code is executed. Say, analysis of requirements etc. Validation is dynamic. Code is executed with scenarios present in test cases.

21. What is test plan and explain its contents?

Ans: Test plan is a document which contains the scope for testing the application and what to be tested, when to be tested and who to test.

22. Advantages of automation over manual testing?

Ans : Time, resource and Money

23. What is ADhoc testing?

Ans : AdHoc means doing something which is not planned.

24. What is mean by release notes?

Ans: 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.

25. Scalability testing comes under in which tool?

Ans: Scalability testing comes under performance testing. Load testing, scalability testing both are same.

26. What is the difference between Bug and Defect?

Ans: Bug: Deviation from the expected result. Defect: Problem in algorithm leads to failure.

A Mistake in code is called Error.

Due to Error in coding, test engineers are getting mismatches in application is called defect.

If defect accepted by development team to solve is called Bug.

27. What is hot fix?

Ans: A hot fix is a single, cumulative package that includes one or more files that are used to address a problem in a software product. Typically, hot fixes are made to address a specific customer situation and may not be distributed outside the customer organization.

Bug found at the customer place which has high priority.

28. What is the difference between functional test cases and comparability test cases?

Ans: There are no Test Cases for Compatibility Testing; in Compatibility Testing we are Testing an application in different Hardware and software. If it is wrong plz let me know.

29. What is Acid Testing?

Ans: ACID Means:

ACID testing is related to testing a transaction.

A-Atomicity

C-Consistent

I-Isolation

D-Durable

Mostly this will be done database testing.

30. What is the main use of preparing a traceability matrix?

Ans: To Cross verify the prepared test cases and test scripts with user requirements.

To monitor the changes, enhance occurred during the development of the project.

Traceability matrix is prepared in order to cross check the test cases designed against each requirement, hence giving an opportunity to verify that all the requirements are covered in testing the application.




what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics

Software Testing Basics and Basic Interview Questions

Software Testing Basics and Basic Interview Questions

Unknown   February 27, 2014   Comment  

Here we are providing what is Software Testing, Software Testing Basics, Software Testing Interview Questions and Software Testing Tutorials. Here in this page we are explaining about what is Soft Ware, Product and Project. And also Along with What is Deference between Project and Product, Why Testing is Necessary Information.

What is Software Testing?

Testing is the Process of Verifying or we developing Right Product or Not and also Validating does the Developed product is right or Not. Verification and Validation is Called Software Testing.

Software Testing = Verification (WBT)+Validation(BBT)

Testing is the Process, Where Tester intention is find out number of Defects, Uncovered Functionality as uncovered errors in a Given Software.

Testing will be done after getting initial Build from Developer, Before Releasing a Product in to Production.

Why Testing is Necessary?

Required:

* Because software is Likely to Have Faults.

* To Learn About the reliability of the Software.

* Because failures can be very expensive.

* To avoid being “Misused” by Customers.

* To Stay in Business.

Not Required:

·         * To fill the time between Delivery of the Software and the release date.

·         * Because Testing is included in the Project Plane.

Software:

A set of Programs and Minimal Data to Run a System is called Software.

Software Types:

·         Accounting Software.

·         Email Software.

·         Mobile and etc.

Product:

Developing software for Multiple Customers developing upon Current Market Technology is Called Product.

Example:  Mobiles, MS Office, MS Windows etc.

Project or Application:

Developing a Software for Specific Customer developing upon own Business Requirement is Called Project.

Example:

Health care

Software Testing Types:

Mainly Software Testing is Two Types, There are

·         Manual Testing

·         Automation Testing

Software Testing Interview Questions

Manual Testing Basics and Manual Testing Interview Questions:

Explanation of some common software testing terms?

Testing objectives include

1. Testing is a process of executing a program with the intent of finding an error.

2. A good test case is one that has a high probability of finding an as yet undiscovered error.

3. A successful test is one that uncovers an as yet undiscovered error.

Testing should systematically uncover different classes of errors in a minimum amount of time and with a minimum amount of effort. A secondary benefit of testing is that it demonstrates that the software appears to be working as stated in the specifications. The data collected through testing can also provide an indication of the software’s reliability and quality. But, testing cannot show the absence of defect — it can only show that software defects are present.

White Box Testing

White box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Test cases can be derived that

1. Guarantee that all independent paths within a module have been exercised at least once,

2. Exercise all logical decisions on their true and false sides,

3. Execute all loops at their boundaries and within their operational bounds, and

4. Exercise internal data structures to ensure their validity.

The Nature of Software Defects

Logic errors and incorrect assumptions are inversely proportional to the probability that a program path will be executed. General processing tends to be well understood while special case processing tends to be prone to errors.

We often believe that a logical path is not likely to be executed when it may be executed on a regular basis. Our unconscious assumptions about control flow and data lead to design errors that can only be detected by path testing.

Typographical errors are random.

Basis Path Testing

This method enables the designer to derive a logical complexity measure of a procedural design and use it as a guide for defining a basis set of execution paths. Test cases that exercise the basis set are guaranteed to execute every statement in the program at least once during testing.

Flow Graphs

Flow graphs can be used to represent control flow in a program and can help in the derivation of the basis set. Each flow graph node represents one or more procedural statements. The edges between nodes represent flow of control. An edge must terminate at a node, even if the node does not represent any useful procedural statements. A region in a flow graph is an area bounded by edges and nodes. Each node that contains a condition is called a predicate node. Cyclomatic complexity is a metric that provides a quantitative measure of the logical complexity of a program. It defines the number of independent paths in the basis set and thus provides an upper bound for the number of tests that must be performed.

The Basis Set

An independent path is any path through a program that introduces at least one new set of processing statements (must move along at least one new edge in the path). The basis set is not unique. Any number of different basis sets can be derived for a given procedural design. Cyclomatic complexity, V(G), for a flow graph G is equal to

1. The number of regions in the flow graph.

2. V(G) = E - N + 2 where E is the number of edges and N is the number of nodes.

3. V(G) = P + 1 where P is the number of predicate nodes.

Deriving Test Cases

1. From the design or source code, derive a flow graph.

2. Determine the cyclomatic complexity of this flow graph.

3. Even without a flow graph, V(G) can be determined by counting the number of conditional statements in the code.

4. Determine a basis set of linearly independent paths.

5. Predicate nodes are useful for determining the necessary paths.

6. Prepare test cases that will force execution of each path in the basis set.

7. Each test case is executed and compared to the expected results.

Automating Basis Set Derivation

The derivation of the flow graph and the set of basis paths is amenable to automation. A software tool to do this can be developed using a data structure called a graph matrix. A graph matrix is a square matrix whose size is equivalent to the number of nodes in the flow graph. Each row and column correspond to a particular node and the matrix corresponds to the connections (edges) between nodes. By adding a link weight to each matrix entry, more information about the control flow can be captured. In its simplest form, the link weight is 1 if an edge exists and 0 if it does not. But other types of link weights can be represented:

• The probability that an edge will be executed,

• The processing time expended during link traversal,

• The memory required during link traversal, or

• The resources required during link traversal.

Graph theory algorithms can be applied to these graph matrices to help in the analysis necessary to produce the basis set.

Loop Testing

This white box technique focuses exclusively on the validity of loop constructs. Four different classes of loops can be defined:

1. Simple loops,

2. Nested loops,

3. Concatenated loops, and

4. Unstructured loops.

Simple Loops

The following tests should be applied to simple loops where n is the maximum number of allowable passes through the loop:

1. Skip the loop entirely,

2. Only pass once through the loop,

3. M passes through the loop where m < n,

4. n - 1, n, n + 1 passes through the loop.

Nested Loops

The testing of nested loops cannot simply extend the technique of simple loops since this would result in a geometrically increasing number of test cases. One approach for nested loops:

1. Start at the innermost loop. Set all other loops to minimum values.

2. Conduct simple loop tests for the innermost loop while holding the outer loops at their minimums. Add tests for out-of-range or excluded values.

3. Work outward, conducting tests for the next loop while keeping all other outer loops at minimums and other nested loops to typical values.

4. Continue until all loops have been tested.

Concatenated Loops

Concatenated loops can be tested as simple loops if each loop is independent of the others. If they are not independent (e.g. the loop counter for one is the loop counter for the other), then the nested approach can be used.

Unstructured Loops

This type of loop should be redesigned not tested!!!

Other White Box Techniques

Other white box testing techniques include:

1. Condition testing

 Exercises the logical conditions in a program.

2. Data flow testing

 Selects test paths according to the locations of definitions and uses of variables in the program.

Black Box Testing

Introduction

Black box testing attempts to derive sets of inputs that will fully exercise all the functional requirements of a system. It is not an alternative to white box testing. This type of testing attempts to find errors in the following categories:

1. Incorrect or missing functions,

2. Interface errors,

3. Errors in data structures or external database access,

4. Performance errors, and

5. Initialization and termination errors.

Tests are designed to answer the following questions:

1. How is the function’s validity tested?

2. What classes of input will make good test cases?

3. Is the system particularly sensitive to certain input values?

4. How are the boundaries of a data class isolated?

5. What data rates and data volume can the system tolerate?

6. What effect will specific combinations of data have on system operation?

White box testing should be performed early in the testing process, while black box testing tends to be applied during later stages. Test cases should be derived which

1. Reduce the number of additional test cases that must be designed to achieve reasonable testing, and

2. Tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.

Equivalence Partitioning

This method divides the input domain of a program into classes of data from which test cases can be derived. Equivalence partitioning strives to define a test case that uncovers classes of errors and thereby reduces the number of test cases needed. It is based on an evaluation of equivalence classes for an input condition. An equivalence class represents a set of valid or invalid states for input conditions.

Equivalence classes may be defined according to the following guidelines:

1. If an input condition specifies a range, one valid and two invalid equivalence classes are defined.

2. If an input condition requires a specific value, then one valid and two invalid equivalence classes are defined.

3. If an input condition specifies a member of a set, then one valid and one invalid equivalence class are defined.

4. If an input condition is Boolean, then one valid and one invalid equivalence class are defined.

Boundary Value Analysis

This method leads to a selection of test cases that exercise boundary values. It complements equivalence partitioning since it selects test cases at the edges of a class. Rather than focusing on input conditions solely, BVA derives test cases from the output domain also. BVA guidelines include:

1. For input ranges bounded by a and b, test cases should include values a and b and just above and just below a and b respectively.

2. If an input condition specifies a number of values, test cases should be developed to exercise the minimum and maximum numbers and values just above and below these limits.

3. Apply guidelines 1 and 2 to the output.

4. If internal data structures have prescribed boundaries, a test case should be designed to exercise the data structure at its boundary.

Cause-Effect Graphing Techniques

Cause-effect graphing is a technique that provides a concise representation of logical conditions and corresponding actions. There are four steps:

1. Causes (input conditions) and effects (actions) are listed for a module and an identifier is assigned to each.

2. A cause-effect graph is developed.

3. The graph is converted to a decision table.

4. Decision table rules are converted to test cases.

Qn. Explain the Manual testing process?

Manual Testing Process:

Process is a roadmap to develop the project is consists a number of sequential steps.

Software Testing Life Cycle:

• Test Plan

• Test Development

• Test Execution

• Analyze Results

• Defect Tracking

• Summaries Report

Test Plan:

It is a document which describes the testing environment, purpose, scope, objectives, test strategy, schedules, mile stones, testing tool, roles and responsibilities, risks, training, staffing and who is going to test the application, what type of tests should be performed and how it will track the defects.

Test Development:

• Preparing test cases

• Preparing test data

• Preparing test procedure

• Preparing test scenario

• Writing test script

Test Execution:

In this phase we execute the documents those are prepared in test development phase.

Analyze result:

Once executed documents will get results either pass or fail. we need to analyse the results during this phase.

Defect Tracking:

Whenever we get defect on the application we need to prepare the bug report file and forwards to Test Team Lead and Dev Team. The Dev Team will fix the bug. Again we have to test the application. This cycle repeats till we get the software with our defects.

Summaries Reports:

• Test Reports

• Bug Reports

• Test Documentation

what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics