QTP Training

qtp test

2012-05-23T19:57:00.001-07:00

QTP Complete Reference

Step by Step QTP Guide for beginners as well as advanced learners. It explains QTP Tool fundamentals and features in detailed manner. It covers QTP tool window keyelements, QTP test process, Recording and Running tests,Enhancing tests, Debugging Tests, Analyzing Test Results and Reporting Defects.

It describes QTP important features like Step Generator, Sychronization, Parameterization, Recovery scenarios and Object Identification Configuration.

An overview on Test Automation

QTP Basic features

Add-in Manager

Key elements of QTP

Test Pane

QTP Commands

QTP Test Process

Recording Tests

Keyword Driven Methodology

Test Object Model

Object Repository

Object Identification Configuration

QTP Test Methods

Data Table Methods

Descriptive Programming

Enhancing Tests

Inserting Checkpoints

Inserting Output values

Parameterization

Synchronization

Inserting Transaction Points

Step Generator

Adding Comments

Inserting Flow Control Statements

Debugging Tests

Running/Executing Tests

Analyzing Test Results & Reporting

Reporting Defects

Actions

Functions

Environment Variables

Regular Expressions

Virtual Object Configuration

Batching Testing

Recovery Scenarios

File System Operations

Database connections

Automation Object Model

Dynamic Handling of Object Repositories

QTP Performance Tips

****************************************

QTP Scripting

QTP Tests in VB Script orientation provides a real-time approach on Scripting. It explains Flat file scripts, Excel Scripts, GUI Scripts, Web scripts, Database scripts and xml scripts with syntax and examples.

****************************************

File System Scripts

Flat File Scripts

Database Scripts-I

Database Scripts-II

Excel Scripts

GUI Scripts

Web Scripts

Web Scripts -II

QTP Real-time Script Examples

Network Administration

System Administration

Power point Scripts

Word Scripts

XML Scripts

QTP Skills

Error Handling in QTP
****************************

VB Script for QTP

It explains VB Script in QTP orientation, It covers all most all VB Script Fundamentals and Features.

It describes, Variables, constants declarations, usage of operators, VB Script flow control statements, Procedures, Coding conventions, Regular Expressions, File system Operations, Database Operations etc..

****************************************

Scripting Languages Vs Programming Languages

VB Script Fundamentals & Features

Comments

VB Script Variables

VB Script Data Types

VB Script Operators

Input/Output Operations

VB Script Constants

VB Script Conditional Statements

Loop through Code

VB Script Statements

VB Script Procedures

VB Script Errors

VB Script Built-In Functions

User Defined Functions

Regular Expressions

VB Script Methods

VB Script Objects

VB Script Coding Conventions

VB Script Classes

VB Script Keywords

VB Script syntax rules and guidelines

VB Script General Examples

VB Script General Examples-II

VB Script Glossary

QTP Online Training

QTP Training (Basics to Advanced) by G C Reddy.

******************************************

QTP Framework

This section provides concepts on How to implement Automation Framework. It explains about Automation Infrastructure development, Resources creation, Driver script creation, Initialization script creation etc.

It describes data driven framework, keyword driven framework and Hybrid framework in detailed manner. It also provides Test estimations, Approvals, Reporting, Organizing and maintaining frameworks.

**********************************************

QTP Interview Questions

QTP Model Resumes
This section provides, Resume preparation guidelines for fresher as well as experienced. It provides some model QTP Resumes for reference.

QTP Job News
This section Provides QTP Job news weekly. Information can be collected by Employers, Consultants and employees. QTP Professionals can use this information and their resumes directly to Employer's and consultants mail ids.

QTP Certification

This section provides HP QTP Certification guidelines and model Questions, It useful for QTP test professionals for preparing Certification exam.
QTP Training Programs

This section provides information on variou QTP Training programs like QTP Basics program for beginners, Advanced program for working people, QTP Framework, and VB Script for QTP that conducted by gcreddy.com

Manual Testing Documents

This section Provides link to our another website gcreddy.net, there you can get Manual Testing Information like, Software Testing Guide, Manual Testing Interview question and answers, Test management guidelines, Test planning, Test design and other documents.

*******************************************

Quality Center

This Section Provides Quality Center Fundamentals and features; Site Administration, Creating Domains, Projects, and Users. Creating Requirements, Designing Manual & Automated Tests, Executing Manual and Automated Tests and Entering defects. Sending Defects directly from QTP Result window.

**********************************************************

LoadRunner

This section provides LoadRunner tool Fundamentals and Features; Vuser generator, Controller, Load Generator, Analysis and LoadRunner Interview Questions.

*********************************************************

QTP Other Topics

This section provides QTP Related articles and other information like, challenges in Test Automation using QTP, Migrating Test scripts from old version to New version, QTP trends, enhancements, New release information, Browser compatibility issues etc..

QTP Software Download Link

SQL Server Guide

Software Testing Documents

Documents on Unit Testing, Web Testing, Software Testing Artifacts, Software Test Process Etc..

QTP Training in Scripting Orientation

QA Testing questions

2012-05-23T19:56:00.004-07:00

QA Testing questions

Q: How can software QA processes be implemented without stifling productivity?

A: Implement QA processes slowly over time. Use consensus to reach agreement on processes and adjust and experiment as an organization grows and matures. Productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection. Panics and burnout will decrease and there will be improved focus and less wasted effort.

At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings and promote training as part of the QA process.

However, no one, especially talented technical types, like bureaucracy and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug fixing and calming of irate customers.
Q: What if the organization is growing so fast that fixed QA processes are impossible?

A: This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than...
•    Hire good people (i.e. hire Rob Davis)
•    Ruthlessly prioritize quality issues and maintain focus on the customer;
•    Everyone in the organization should be clear on what quality means to the customer.

Q: Why do you recommend that we test during the design phase?

A: Because testing during the design phase can prevent defects later on. We recommend verifying three things...
1.    Verify the design is good, efficient, compact, testable and maintainable.
2.    Verify the design meets the requirements and is complete (specifies all relationships between modules, how to pass data, what happens in exceptional circumstances, starting state of each module and how to guarantee the state of each module).
3.    Verify the design incorporates enough memory, I/O devices and quick enough runtime for the final product.

Q: How is testing affected by object-oriented designs?

A: A well-engineered object-oriented design can make it easier to trace from code to internal design to functional design to requirements. While there will be little affect on black box testing (where an understanding of the internal design of the application is unnecessary), white-box testing can be oriented to the application's objects. If the application was well designed this can simplify test design.

Q: What is quality assurance?

A: Quality Assurance ensures all parties concerned with the project adhere to the process and procedures, standards and templates and test readiness reviews.

Q: What is black box testing?

A: Black box testing is functional testing, not based on any knowledge of internal software design or code. Black box testing are based on requirements and functionality.

Q: What is white box testing?

A: White box testing is based on knowledge of the internal logic of an application's code. Tests are based on coverage of code statements, branches, paths and conditions.

Q: What is unit testing?

A: Unit testing is the first level of dynamic testing and is first the responsibility of developers and then that of the test engineers.

Unit testing is performed after the expected test results are met or differences are explainable/acceptable.

Q: What is functional testing?

A: Functional testing is black-box type of testing geared to functional requirements of an application. Test engineers *should* perform functional testing.

Q: What is usability testing?

A: Usability testing is testing for 'user-friendliness'. Clearly this is subjective and depends on the targeted end-user or customer. User interviews, surveys, video recording of user sessions and other techniques can be used. Programmers and developers are usually not appropriate as usability testers.

Q: What is incremental integration testing?

A: Incremental integration testing is continuous testing of an application as new functionality is recommended. This may require that various aspects of an application's functionality are independent enough to work separately, before all parts of the program are completed, or that test drivers are developed as needed.

Incremental testing may be performed by programmers, software engineers, or test engineers.

Q: What is parallel/audit testing?

A: Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly.

Q: What is integration testing?

A: Upon completion of unit testing, integration testing begins. Integration testing is black box testing. The purpose of integration testing is to ensure distinct components of the application still work in accordance to customer requirements.

Test cases are developed with the express purpose of exercising the interfaces between the components. This activity is carried out by the test team.

Integration testing is considered complete, when actual results and expected results are either in line or differences are explainable/acceptable based on client input.

Q: What is system testing?

A: System testing is black box testing, performed by the Test Team, and at the start of the system testing the complete system is configured in a controlled environment.

The purpose of system testing is to validate an application's accuracy and completeness in performing the functions as designed.

System testing simulates real life scenarios that occur in a "simulated real life" test environment and test all functions of the system that are required in real life.

System testing is deemed complete when actual results and expected results are either in line or differences are explainable or acceptable, based on client input.
Upon completion of integration testing, system testing is started. Before system testing, all unit and integration test results are reviewed by Software QA to ensure all problems have been resolved. For a higher level of testing it is important to understand unresolved problems that originate at unit and integration test levels.

You CAN learn system testing, with little or no outside help. Get CAN get free information. Click on a link!

Q: What is end-to-end testing?

A: Similar to system testing, the *macro* end of the test scale is testing a complete application in a situation that mimics real world use, such as interacting with a database, using network communication, or interacting with other hardware, application, or system.

Q: What is regression testing?

A: The objective of regression testing is to ensure the software remains intact. A baseline set of data and scripts is maintained and executed to verify changes introduced during the release have not "undone" any previous code. Expected results from the baseline are compared to results of the software under test. All discrepancies are highlighted and accounted for, before testing proceeds to the next level.

Q: What is sanity testing?

A: Sanity testing is performed whenever cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.

It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.

Testing FAQ

2012-05-23T19:56:00.003-07:00

Manual Testing Interview Questions

Q: What is performance testing?

A: Although performance testing is described as a part of system testing, it can be regarded as a distinct level of testing. Performance testing verifies loads, volumes and response times, as defined by requirements.

Q: What is load testing?

A: Load testing is testing an application under heavy loads, such as the testing of a web site under a range of loads to determine at what point the system response time will degrade or fail.

Q: What is installation testing?

A: Installation testing is testing full, partial, upgrade, or install/uninstall processes. The installation test for a release is conducted with the objective of demonstrating production readiness.
This test includes the inventory of configuration items, performed by the application's System Administration, the evaluation of data readiness, and dynamic tests focused on basic system functionality. When necessary, a sanity test is performed, following installation testing.

Q: What is security/penetration testing?

A: Security/penetration testing is testing how well the system is protected against unauthorized internal or external access, or willful damage.

This type of testing usually requires sophisticated testing techniques.

Q: What is recovery/error testing?

A: Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Q: What is compatibility testing?

A: Compatibility testing is testing how well software performs in a particular hardware, software, operating system, or network
This test includes the inventory of configuration items, performed by the application's System Administration, the evaluation of data readiness, and dynamic tests focused on basic system functionality. When necessary, a sanity test is performed, following installation testing.

Q: What is security/penetration testing?

Q: What is recovery/error testing?

A: Recovery/error testing is testing how well a system recovers from crashes, hardware failures, or other catastrophic problems.

Q: What is compatibility testing?

A: Compatibility testing is testing how well software performs in a particular hardware, software, operating system, or network

Q: What is comparison testing?

A: Comparison testing is testing that compares software weaknesses and strengths to those of competitors' products.

Q: What is acceptance testing?

A: Acceptance testing is black box testing that gives the client/customer/project manager the opportunity to verify the system functionality and usability prior to the system being released to production.

The acceptance test is the responsibility of the client/customer or project manager, however, it is conducted with the full support of the project team. The test team also works with the client/customer/project manager to develop the acceptance criteria.

Q: What is alpha testing?

A: Alpha testing is testing of an application when development is nearing completion. Minor design changes can still be made as a result of alpha testing. Alpha testing is typically performed by a group that is independent of the design team, but still within the company, e.g. in-house software test engineers, or software QA engineers.

Q: What is beta testing?

A: Beta testing is testing an application when development and testing are essentially completed and final bugs and problems need to be found before the final release. Beta testing is typically performed by end-users or others, not programmers, software engineers, or test engineers.

Q: What is a Test/QA Team Lead?

A: The Test/QA Team Lead coordinates the testing activity, communicates testing status to management and manages the test team.

Q: What testing roles are standard on most testing projects?

A: Depending on the organization, the following roles are more or less standard on most testing projects: Testers, Test Engineers, Test/QA Team Lead, Test/QA Manager, System Administrator, Database Administrator, Technical Analyst, Test Build Manager and Test Configuration Manager.

Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of Technical Analyst, Test Build Manager and Test Configuration Manager.

You CAN get a job in testing. Click on a link!

Q: What is a Test Engineer?

A: We, test engineers, are engineers who specialize in testing. We, test engineers, create test cases, procedures, scripts and generate data. We execute test procedures and scripts, analyze standards of measurements, evaluate results of system/integration/regression testing. We also...
•    Speed up the work of the development staff;
•    Reduce your organization's risk of legal liability;
•    Give you the evidence that your software is correct and operates properly;
•    Improve problem tracking and reporting;
•    Maximize the value of your software;
•    Maximize the value of the devices that use it;
•    Assure the successful launch of your product by discovering bugs and design flaws, before users get discouraged, before shareholders loose their cool and before employees get bogged down;
•    Help the work of your development staff, so the development team can devote its time to build up your product;
•    Promote continual improvement;
•    Provide documentation required by FDA, FAA, other regulatory agencies and your customers;
•    Save money by discovering defects 'early' in the design process, before failures occur in production, or in the field;
•    Save the reputation of your company by discovering bugs and design flaws; before bugs and design flaws damage the reputation of your company.

Q: What is a Test Build Manager?

A: Test Build Managers deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware.

Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Test Build Manager.

Q: What is a System Administrator?

A: Test Build Managers, System Administrators, Database Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware.

Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a System Administrator.

Q: What is a Database Administrator?

A: Test Build Managers, System Administrators and Database Administrators deliver current software versions to the test environment, install the application's software and apply software patches, to both the application and the operating system, set-up, maintain and back up test environment hardware. Depending on the project, one person may wear more than one hat. For instance, a Test Engineer may also wear the hat of a Database Administrator.

Q: What is a Technical Analyst?

A: Technical Analysts perform test assessments and validate system/functional test requirements. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Technical Analyst.

Q: What is a Test Configuration Manager?

A: Test Configuration Managers maintain test environments, scripts, software and test data. Depending on the project, one person may wear more than one hat. For instance, Test Engineers may also wear the hat of a Test Configuration Manager.

Q: What is a test schedule?

A: The test schedule is a schedule that identifies all tasks required for a successful testing effort, a schedule of all test activities and resource requirements.

Q: What is software testing methodology?

A: One software testing methodology is the use a three step process of...
1.    Creating a test strategy;
2.    Creating a test plan/design; and
3.    Executing tests.
This methodology can be used and molded to your organization's needs. G C Reddy believes that using this methodology is important in the development and ongoing maintenance of his clients' applications.

software testing FAQ

2012-05-23T19:56:00.002-07:00

software testing FAQ

Q: What is the general testing process?

A: The general testing process is the creation of a test strategy (which sometimes includes the creation of test cases), creation of a test plan/design (which usually includes test cases and test procedures) and the execution of tests.

Q: How do you create a test plan/design?

A: Test scenarios and/or cases are prepared by reviewing functional requirements of the release and preparing logical groups of functions that can be further broken into test procedures. Test procedures define test conditions, data to be used for testing and expected results, including database updates, file outputs, report results. Generally speaking...
•    Test cases and scenarios are designed to represent both typical and unusual situations that may occur in the application.
•    Test engineers define unit test requirements and unit test cases. Test engineers also execute unit test cases.
•    It is the test team that, with assistance of developers and clients, develops test cases and scenarios for integration and system testing.
•    Test scenarios are executed through the use of test procedures or scripts.
•    Test procedures or scripts define a series of steps necessary to perform one or more test scenarios.
•    Test procedures or scripts include the specific data that will be used for testing the process or transaction.
•    Test procedures or scripts may cover multiple test scenarios.
•    Test scripts are mapped back to the requirements and traceability matrices are used to ensure each test is within scope.
•    Test data is captured and base lined, prior to testing. This data serves as the foundation for unit and system testing and used to exercise system functionality in a controlled environment.
•    Some output data is also base-lined for future comparison. Base-lined data is used to support future application maintenance via regression testing.
•    A pretest meeting is held to assess the readiness of the application and the environment and data to be tested. A test readiness document is created to indicate the status of the entrance criteria of the release.
Inputs for this process:
•    Approved Test Strategy Document.
•    Test tools, or automated test tools, if applicable.
•    Previously developed scripts, if applicable.
•    Test documentation problems uncovered as a result of testing.
•    A good understanding of software complexity and module path coverage, derived from general and detailed design documents, e.g. software design document, source code, and software complexity data.
Outputs for this process:
•    Approved documents of test scenarios, test cases, test conditions, and test data.
•    Reports of software design issues, given to software developers for correction.

Q: How do you execute tests?

A: Execution of tests is completed by following the test documents in a methodical manner. As each test procedure is performed, an entry is recorded in a test execution log to note the execution of the procedure and whether or not the test procedure uncovered any defects. Checkpoint meetings are held throughout the execution phase. Checkpoint meetings are held daily, if required, to address and discuss testing issues, status and activities.
•    The output from the execution of test procedures is known as test results. Test results are evaluated by test engineers to determine whether the expected results have been obtained. All discrepancies/anomalies are logged and discussed with the software team lead, hardware test lead, programmers, software engineers and documented for further investigation and resolution. Every company has a different process for logging and reporting bugs/defects uncovered during testing.
•    A pass/fail criteria is used to determine the severity of a problem, and results are recorded in a test summary report. The severity of a problem, found during system testing, is defined in accordance to the customer's risk assessment and recorded in their selected tracking tool.
•    Proposed fixes are delivered to the testing environment, based on the severity of the problem. Fixes are regression tested and flawless fixes are migrated to a new baseline. Following completion of the test, members of the test team prepare a summary report. The summary report is reviewed by the Project Manager, Software QA Manager and/or Test Team Lead.
•    After a particular level of testing has been certified, it is the responsibility of the Configuration Manager to coordinate the migration of the release software components to the next test level, as documented in the Configuration Management Plan. The software is only migrated to the production environment after the Project Manager's formal acceptance.
•    The test team reviews test document problems identified during testing, and update documents where appropriate.
Inputs for this process:
•    Approved test documents, e.g. Test Plan, Test Cases, Test Procedures.
•    Test tools, including automated test tools, if applicable.
•    Developed scripts.
•    Changes to the design, i.e. Change Request Documents.
•    Test data.
•    Availability of the test team and project team.
•    General and Detailed Design Documents, i.e. Requirements Document, Software Design Document.
•    A software that has been migrated to the test environment, i.e. unit tested code, via the Configuration/Build Manager.
•    Test Readiness Document.
•    Document Updates.
Outputs for this process:
•    Log and summary of the test results. Usually this is part of the Test Report. This needs to be approved and signed-off with revised testing deliverables.
•    Changes to the code, also known as test fixes.
•    Test document problems uncovered as a result of testing. Examples are Requirements document and Design Document problems.
•    Reports on software design issues, given to software developers for correction. Examples are bug reports on code issues.
•    Formal record of test incidents, usually part of problem tracking.
•    Base-lined package, also known as tested source and object code, ready for migration to the next level.

Q: How do you create a test strategy?

A: The test strategy is a formal description of how a software product will be tested. A test strategy is developed for all levels of testing, as required. The test team analyzes the requirements, writes the test strategy and reviews the plan with the project team. The test plan may include test cases, conditions, the test environment, a list of related tasks, pass/fail criteria and risk assessment.
Inputs for this process:
•    A description of the required hardware and software components, including test tools. This information comes from the test environment, including test tool data.
•    A description of roles and responsibilities of the resources required for the test and schedule constraints. This information comes from man-hours and schedules.
•    Testing methodology. This is based on known standards.
•    Functional and technical requirements of the application. This information comes from requirements, change request, technical and functional design documents.
•    Requirements that the system can not provide, e.g. system limitations.
Outputs for this process:
•    An approved and signed off test strategy document, test plan, including test cases.
•    Testing issues requiring resolution. Usually this requires additional negotiation at the project management level.

Q: What is security clearance?

A: Security clearance is a process of determining your trustworthiness and reliability before granting you access to national security information.

Q: What are the levels of classified access?

A: The levels of classified access are confidential, secret, top secret, and sensitive compartmented information, of which top secret is the highest.

What's a 'test plan'?

A software project test plan is a document that describes the objectives, scope, approach, and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the 'why' and 'how' of product validation. It should be thorough enough to be useful but not so thorough that no one outside the test group will read it. The following are some of the items that might be included in a test plan, depending on the particular project:

* Title

* Identification of software including version/release numbers.

* Revision history of document including authors, dates, approvals.

* Table of Contents.

* Purpose of document, intended audience

* Objective of testing effort

* Software product overview

* Relevant related document list, such as requirements, design documents, other test plans, etc.

* Relevant standards or legal requirements

* Traceability requirements

* Relevant naming conventions and identifier conventions

* Overall software project organization and personnel/contact-info/responsibilties

* Test organization and personnel/contact-info/responsibilities

* Assumptions and dependencies

* Project risk analysis

* Testing priorities and focus

* Scope and limitations of testing

* Test outline - a decomposition of the test approach by test type, feature, functionality, process, system, module, etc. as applicable

* Outline of data input equivalence classes, boundary value analysis, error classes

* Test environment - hardware, operating systems, other required software, data configurations, interfaces to other systems

* Test environment validity analysis - differences between the test and production systems and their impact on test validity.

* Test environment setup and configuration issues

* Software migration processes

* Software CM processes

• * Test data setup requirements

* Database setup requirements

* Outline of system-logging/error-logging/other capabilities, and tools such as screen capture software, that will be used to help describe and report bugs

* Discussion of any specialized software or hardware tools that will be used by testers to help track the cause or source of bugs

* Test automation - justification and overview

* Test tools to be used, including versions, patches, etc.

* Test script/test code maintenance processes and version control

* Problem tracking and resolution - tools and processes

* Project test metrics to be used

* Reporting requirements and testing deliverables

* Software entrance and exit criteria

* Initial sanity testing period and criteria

* Test suspension and restart criteria

* Personnel allocation

* Personnel pre-training needs

* Test site/location

* Outside test organizations to be utilized and their purpose, responsibilties, deliverables, contact persons, and coordination issues.

* Relevant proprietary, classified, security, and licensing issues.

* Open issues

* Appendix - glossary, acronyms, etc.

What's a 'test case'?

* A test case is a document that describes an input, action, or event and an expected response, to determine if a feature of an application is working correctly. A test case should contain particulars such as test case identifier, test case name, objective, test conditions/setup, input data requirements, steps, and expected results.

* Note that the process of developing test cases can help find problems in the requirements or design of an application, since it requires completely thinking through the operation of the application. For this reason, it's useful to prepare test cases early in the development cycle if possible.

What should be done after a bug is found?

* The bug needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested, and determinations made regarding requirements for regression testing to check that fixes didn't create problems elsewhere. If a problem-tracking system is in place, it should encapsulate these processes. A variety of commercial problem-tracking/management software tools are available (see the 'Tools' section for web resources with listings of such tools). The following are items to consider in the tracking process:

* Complete information such that developers can understand the bug, get an idea of it's severity, and reproduce it if necessary.
* Bug identifier (number, ID, etc.)

* Current bug status (e.g., 'Released for Retest', 'New', etc.)

* The application name or identifier and version

* The function, module, feature, object, screen, etc. where the bug occurred

* Environment specifics, system, platform, relevant hardware specifics

* Test case name/number/identifier

* One-line bug description

* Full bug description

* Description of steps needed to reproduce the bug if not covered by a test case or if the developer doesn't have easy access to the test case/test script/test tool

* Names and/or descriptions of file/data/messages/etc. used in test

* File excerpts/error messages/log file excerpts/screen shots/test tool logs that would be helpful in finding the cause of the problem

* Severity estimate (a 5-level range such as 1-5 or 'critical'-to-'low' is common)

* Was the bug reproducible?

* Tester name

* Test date

* Bug reporting date

* Name of developer/group/organization the problem is assigned to

* Description of problem cause

* Description of fix

* Code section/file/module/class/method that was fixed

* Date of fix

* Application version that contains the fix

* Tester responsible for retest

* Retest date

* Retest results

* Regression testing requirements

* Tester responsible for regression tests

* Regression testing results

* A reporting or tracking process should enable notification of appropriate personnel at various stages. For instance, testers need to know when retesting is needed, developers need to know when bugs are found and how to get the needed information, and reporting/summary capabilities are needed for managers.

What if the software is so buggy it can't really be tested at all?

* The best bet in this situation is for the testers to go through the process of reporting whatever bugs or blocking-type problems initially show up, with the focus being on critical bugs. Since this type of problem can severely affect schedules, and indicates deeper problems in the software development process (such as insufficient unit testing or insufficient integration testing, poor design, improper build or release procedures, etc.) managers should be notified, and provided with some documentation as evidence of the problem.

How can it be known when to stop testing?

This can be difficult to determine. Many modern software applications are so complex, and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are:

* Deadlines (release deadlines, testing deadlines, etc.)

* Test cases completed with certain percentage passed

* Test budget depleted

* Coverage of code/functionality/requirements reaches a specified point

* Bug rate falls below a certain level

* Beta or alpha testing period ends

What if there isn't enough time for thorough testing?

* Use risk analysis to determine where testing should be focused. Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects. This requires judgement skills, common sense, and experience. (If warranted, formal methods are also available.) Considerations can include:

* Which functionality is most important 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?

What if the project isn't big enough to justify extensive testing?

* Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the same considerations as described previously in 'What if there isn't enough time for thorough testing?' apply. The tester might then do ad hoc testing, or write up a limited test plan based on the risk analysis.

What can be done if requirements are changing continuously?

A common problem and a major headache

* Work with the project's stakeholders early on to understand how requirements might change so that alternate test plans and strategies can be worked out in advance, if possible.

* It's helpful if the application's initial design allows for some adaptability so that later changes do not require redoing the application from scratch.

* If the code is well-commented and well-documented this makes changes easier for the developers.

* Use rapid prototyping whenever possible to help customers feel sure of their requirements and minimize changes.

* The project's initial schedule should allow for some extra time commensurate with the possibility of changes.

* Try to move new requirements to a 'Phase 2' version of an application, while using the original requirements for the 'Phase 1' version.

* Negotiate to allow only easily-implemented new requirements into the project, while moving more difficult new requirements into future versions of the application.

* Be sure that customers and management understand the scheduling impacts, inherent risks, and costs of significant requirements changes. Then let management or the customers (not the developers or testers) decide if the changes are warranted - after all, that's their job.

* Balance the effort put into setting up automated testing with the expected effort required to re-do them to deal with changes.

* Try to design some flexibility into automated test scripts.

* Focus initial automated testing on application aspects that are most likely to remain unchanged.

* Devote appropriate effort to risk analysis of changes to minimize regression testing needs.

* Design some flexibility into test cases (this is not easily done; the best bet might be to minimize the detail in the test cases, or set up only higher-level generic-type test plans)

* Focus less on detailed test plans and test cases and more on ad hoc testing (with an understanding of the added risk that this entails).

Manual Testing questions and answers

2012-05-23T19:56:00.001-07:00

Manual Testing questions and answers

• What if the application has functionality that wasn't in the requirements?

* It may take serious effort to determine if an application has significant unexpected or hidden functionality, and it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer. If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only effects areas such as minor improvements in the user interface, for example, it may not be a significant risk.

How can QA processes be implemented without stifling productivity?

* By implementing QA processes slowly over time, using consensus to reach agreement on processes, and adjusting and experimenting as an organization grows and matures, productivity will be improved instead of stifled. Problem prevention will lessen the need for problem detection, panics and burn-out will decrease, and there will be improved focus and less wasted effort. At the same time, attempts should be made to keep processes simple and efficient, minimize paperwork, promote computer-based processes and automated tracking and reporting, minimize time required in meetings, and promote training as part of the QA process. However, no one - especially talented technical types - likes rules or bureacracy, and in the short run things may slow down a bit. A typical scenario would be that more days of planning and development will be needed, but less time will be required for late-night bug-fixing and calming of irate customers. (See the Books section's 'Software QA', 'Software Engineering', and 'Project Management' categories for useful books with more information.)

What if an organization is growing so fast that fixed QA processes are impossible

* This is a common problem in the software industry, especially in new technology areas. There is no easy solution in this situation, other than:

* Hire good people

* Management should 'ruthlessly prioritize' quality issues and maintain focus on the customer

* Everyone in the organization should be clear on what 'quality' means to the customer

How does a client/server environment affect testing?

* Client/server applications can be quite complex due to the multiple dependencies among clients, data communications, hardware, and servers. Thus testing requirements can be extensive. When time is limited (as it usually is) the focus should be on integration and system testing. Additionally, load/stress/performance testing may be useful in determining client/server application limitations and capabilities. There are commercial tools to assist with such testing. (See the 'Tools' section for web resources with listings that include these kinds of test tools.)

How can World Wide Web sites be tested?

* Web sites are essentially client/server applications - with web servers and 'browser' clients. Consideration should be given to the interactions between html pages, TCP/IP communications, Internet connections, firewalls, applications that run in web pages (such as applets, javascript, plug-in applications), and applications that run on the server side (such as cgi scripts, database interfaces, logging applications, dynamic page generators, asp, etc.). Additionally, there are a wide variety of servers and browsers, various versions of each, small but sometimes significant differences between them, variations in connection speeds, rapidly changing technologies, and multiple standards and protocols. The end result is that
• testing for web sites can become a major ongoing effort. Other considerations might include:

How is testing affected by object-oriented designs?

* What are the expected loads on the server (e.g., number of hits per unit time?), and what kind of performance is required under such loads (such as web server response time, database query response times). What kinds of tools will be needed for performance testing (such as web load testing tools, other tools already in house that can be adapted, web robot downloading tools, etc.)?

* Who is the target audience? What kind of browsers will they be using? What kind of connection speeds will they by using? Are they intra- organization (thus with likely high connection speeds and similar browsers) or Internet-wide (thus with a wide variety of connection speeds and browser types)?

* What kind of performance is expected on the client side (e.g., how fast should pages appear, how fast should animations, applets, etc. load and run)?

* Will down time for server and content maintenance/upgrades be allowed? how much?

* Will down time for server and content maintenance/upgrades be allowed? how much?

* How reliable are the site's Internet connections required to be? And how does that affect backup system or redundant connection requirements and testing?

* What processes will be required to manage updates to the web site's content, and what are the requirements for maintaining, tracking, and controlling page content, graphics, links, etc.?

* Which HTML specification will be adhered to? How strictly? What variations will be allowed for targeted browsers?
* Will there be any standards or requirements for page appearance and/or graphics throughout a site or parts of a site?
* How will internal and external links be validated and updated? how often?

* Can testing be done on the production system, or will a separate test system be required? How are browser caching, variations in browser option settings, dial-up connection variabilities, and real-world internet 'traffic congestion' problems to be accounted for in testing?
* How extensive or customized are the server logging and reporting requirements; are they considered an integral part of the system and do they require testing?

* How are cgi programs, applets, javascripts, ActiveX components, etc. to be maintained, tracked, controlled, and tested?
* Pages should be 3-5 screens max unless content is tightly focused on a single topic. If larger, provide internal links within the page.

* The page layouts and design elements should be consistent throughout a site, so that it's clear to the user that they're still within a site.
* Pages should be as browser-independent as possible, or pages should be provided or generated based on the browser-type.
* All pages should have links external to the page; there should be no dead-end pages.
* The page owner, revision date, and a link to a contact person or organization should be included on each page.
What is Extreme Programming and what's it got to do with testing?

* Extreme Programming (XP) is a software development approach for small teams on risk-prone projects with unstable requirements. It was created by Kent Beck who described the approach in his book 'Extreme Programming Explained' (See the Softwareqatest.com Books page.). Testing ('extreme testing') is a core aspect of Extreme Programming. Programmers are expected to write unit and functional test code first - before the application is developed. Test code is under source control along with the rest of the code. Customers are expected to be an integral part of the project team and to help develope scenarios for acceptance/black box testing. Acceptance tests are preferably automated, and are modified and rerun for each of the frequent development iterations. QA and test personnel are also required to be an integral part of the project team. Detailed requirements documentation is not used, and frequent re-scheduling, re-estimating, and re-prioritizing is expected.

Manual Testing Interview Questions

2012-05-23T19:56:00.000-07:00

Manual Testing Interview Questions -6

Q: How do you introduce a new software QA process?

A: It depends on the size of the organization and the risks involved. For large organizations with high-risk projects, a serious management buy-in is required and a formalized QA process is necessary. For medium size organizations with lower risk projects, management and organizational buy-in and a slower, step-by-step process is required. Generally speaking, QA processes should be balanced with productivity, in order to keep any bureaucracy from getting out of hand. For smaller groups or projects, an ad-hoc process is more appropriate. A lot depends on team leads and managers, feedback to developers and good communication is essential among customers, managers, developers, test engineers and testers. Regardless the size of the company, the greatest value for effort is in managing requirement processes, where the goal is requirements that are clear, complete and
testable.

Q: What is the role of documentation in QA?

A: Documentation plays a critical role in QA. QA practices should be documented, so that they are repeatable. Specifications, designs, business rules, inspection reports, configurations, code changes, test plans, test cases, bug reports, user manuals should all be documented. Ideally, there should be a system for easily finding and obtaining of documents and determining what document will have a particular piece of information. Use documentation change management, if possible.

Q: What makes a good test engineer?

A: Good test engineers have a "test to break" attitude. We, good test engineers, take the point of view of the customer; have a strong desire for quality and an attention to detail. Tact and diplomacy are useful in maintaining a cooperative relationship with developers and an ability to communicate with both technical and non-technical people. Previous software development experience is also helpful as it provides a deeper understanding of the software development process, gives the test engineer an appreciation for the developers' point of view and reduces the learning curve in automated test tool programming.

G C Reddy is a good test engineer because he has a "test to break" attitude, takes the point of view of the customer, has a strong desire for quality, has an attention to detail, He's also tactful and diplomatic and has good a communication skill, both oral and written. And he has previous software development experience, too.

Q: What is a test plan?

A: A software project test plan is a document that describes the objectives, scope, approach and focus of a software testing effort. The process of preparing a test plan is a useful way to think through the efforts needed to validate the acceptability of a software product. The completed document will help people outside the test group understand the why and how of product validation. It should be thorough enough to be useful, but not so thorough that none outside the test group will be able to read it.

Q: What is a test case?

A: A test case is a document that describes an input, action, or event and its expected result, in order to determine if a feature of an application is working correctly. A test case should contain particulars such as a...
•    Test case identifier;
•    Test case name;
•    Objective;
•    Test conditions/setup;
•    Input data requirements/steps, and
•    Expected results.
Please note, the process of developing test cases can help find problems in the requirements or design of an application, since it requires you to completely think through the operation of the application. For this reason, it is useful to prepare test cases early in the development cycle, if possible.

Q: What should be done after a bug is found?

A: When a bug is found, it needs to be communicated and assigned to developers that can fix it. After the problem is resolved, fixes should be re-tested. Additionally, determinations should be made regarding requirements, software, hardware, safety impact, etc., for regression testing to check the fixes didn't create other problems elsewhere. If a problem-tracking system is in place, it should encapsulate these determinations. A variety of commercial, problem-tracking/management software tools are available. These tools, with the detailed input of software test engineers, will give the team complete information so developers can understand the bug, get an idea of its severity, reproduce it and fix it.

Q: What is configuration management?

A: Configuration management (CM) covers the tools and processes used to control, coordinate and track code, requirements, documentation, problems, change requests, designs, tools, compilers, libraries, patches, changes made to them and who makes the changes. Rob Davis has had experience with a full range of CM tools and concepts, and can easily adapt to your software tool and process needs.

Q: What if the software is so buggy it can't be tested at all?

A: In this situation the best bet is to have test engineers go through the process of reporting whatever bugs or problems initially show up, with the focus being on critical bugs.

Since this type of problem can severely affect schedules and indicates deeper problems in the software development process, such as insufficient unit testing, insufficient integration testing, poor design, improper build or release procedures, managers should be notified and provided with some documentation as evidence of the problem.

Q: What if there isn't enough time for thorough testing?

A: Since it's rarely possible to test every possible aspect of an application, every possible combination of events, every dependency, or everything that could go wrong, risk analysis is appropriate to most software development projects.

Use risk analysis to determine where testing should be focused. This requires judgment skills, common sense and experience. The checklist should include answers to the following questions:
•    Which functionality is most important 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?

Q: What if the project isn't big enough to justify extensive testing?

A: Consider the impact of project errors, not the size of the project. However, if extensive testing is still not justified, risk analysis is again needed and the considerations listed under "What if there isn't enough time for thorough testing?" do apply. The test engineer then should do "ad hoc" testing, or write up a limited test plan based on the risk analysis.

Q: What can be done if requirements are changing continuously?

A: Work with management early on to understand how requirements might change, so that alternate test plans and strategies can be worked out in advance. It is helpful if the application's initial design allows for some adaptability, so that later changes do not require redoing the application from scratch. Additionally, try to...
•    Ensure the code is well commented and well documented; this makes changes easier for the developers.
•    Use rapid prototyping whenever possible; this will help customers feel sure of their requirements and minimize changes.
•    In the project's initial schedule, allow for some extra time to commensurate with probable changes.
Move new requirements to a 'Phase 2' version of an application and use the original requirements for the 'Phase 1' version.
Negotiate to allow only easily implemented new requirements into the project.
•    Ensure customers and management understand scheduling impacts, inherent risks and costs of significant requirements changes. Then let management or the customers decide if the changes are warranted; after all, that's their job.
•    Balance the effort put into setting up automated testing with the expected effort required to redo them to deal with changes.
•    Design some flexibility into automated test scripts;
•    Focus initial automated testing on application aspects that are most likely to remain unchanged;
•    Devote appropriate effort to risk analysis of changes, in order to minimize regression-testing needs;
•    Design some flexibility into test cases; this is not easily done; the best bet is to minimize the detail in the test cases, or set up only higher-level generic-type test plans;
Focus less on detailed test plans and test cases and more on ad-hoc testing with an understanding of the added risk this entails.

Q: How do you know when to stop testing?

A: This can be difficult to determine. Many modern software applications are so complex and run in such an interdependent environment, that complete testing can never be done. Common factors in deciding when to stop are...
•    Deadlines, e.g. release deadlines, testing deadlines;
•    Test cases completed with certain percentage passed;
•    Test budget has been depleted;
•    Coverage of code, functionality, or requirements reaches a specified point;
•    Bug rate falls below a certain level; or
•    Beta or alpha testing period ends.

Q: What if the application has functionality that wasn't in the requirements?

A: It may take serious effort to determine if an application has significant unexpected or hidden functionality, which it would indicate deeper problems in the software development process. If the functionality isn't necessary to the purpose of the application, it should be removed, as it may have unknown impacts or dependencies that were not taken into account by the designer or the customer.
If not removed, design information will be needed to determine added testing needs or regression testing needs. Management should be made aware of any significant added risks as a result of the unexpected functionality. If the functionality only affects areas, such as minor improvements in the user interface, it may not be a significant risk.

Manual Testing Interview Questions 2

2012-05-22T00:28:00.001-07:00

Manual Testing Interview Questions & Answers

1. What is Acceptance Testing?

Testing conducted to enable a user/customer to determine whether to accept a software product. Normally performed to validate the software meets a set of agreed acceptance criteria.

2. What is Accessibility Testing?

Verifying a product is accessible to the people having disabilities (deaf, blind, mentally disabled etc.).

3. What is Ad-Hoc Testing?

A testing phase where the tester tries to 'break' the system by randomly trying the system's functionality. Can include negative testing as well. See also Monkey Testing.

4. What is Agile Testing?

Testing practice for projects using agile methodologies, treating development as the customer of testing and emphasizing a test-first design paradigm. See also Test Driven Development.

5. What is Application Binary Interface (ABI)?

A specification defining requirements for portability of applications in binary forms across different system platforms and environments.

6. What is Application Programming Interface (API)?

A formalized set of software calls and routines that can be referenced by an application program in order to access supporting system or network services.

7. What is Automated Software Quality (ASQ)?

The use of software tools, such as automated testing tools, to improve software quality.

8. What is Automated Testing?

Testing employing software tools which execute tests without manual intervention. Can be applied in GUI, performance, API, etc. testing. The use of software to control the execution of tests, the comparison of actual outcomes to predicted outcomes, the setting up of test preconditions, and other test control and test reporting functions.

9. What is Backus-Naur Form?

A metalanguage used to formally describe the syntax of a language.

10. What is Basic Block?

A sequence of one or more consecutive, executable statements containing no

branches.

11. What is Basis Path Testing?

A white box test case design technique that uses the algorithmic flow of the program to design tests.

12. What is Basis Set?

The set of tests derived using basis path testing.

13. What is Baseline?

The point at which some deliverable produced during the software engineering process is put under formal change control.

14. What you will do during the first day of job?

What would you like to do five years from now?

15. What is Beta Testing?

Testing of a rerelease of a software product conducted by customers.

16. What is Binary Portability Testing?

Testing an executable application for portability across system platforms and environments, usually for conformation to an ABI specification.

17. What is Black Box Testing?

Testing based on an analysis of the specification of a piece of software without reference to its internal workings. The goal is to test how well the component conforms to the published requirements for the component.

18. What is Bottom Up Testing?

An approach to integration testing where the lowest level components are tested first, then used to facilitate the testing of higher level components. The process is repeated until the component at the top of the hierarchy is tested.

19. What is Boundary Testing?

Test which focus on the boundary or limit conditions of the software being tested. (Some of these tests are stress tests).

20. What is Boundary Value Analysis?

BVA is similar to Equivalence Partitioning but focuses on "corner cases" or values that are usually out of range as defined by the specification. his means that if a function expects all values in range of negative 100 to positive 1000, test inputs would include negative 101 and positive 1001.

21. What is Branch Testing?

Testing in which all branches in the program source code are tested at least once.

22. What is Breadth Testing?

A test suite that exercises the full functionality of a product but does not test features in detail.

23. What is CAST?

Computer Aided Software Testing.

24. What is Capture/Replay Tool?

A test tool that records test input as it is sent to the software under test. The input cases stored can then be used to reproduce the test at a later time. Most commonly applied to GUI test tools.

25. What is CMM?

The Capability Maturity Model for Software (CMM or SW-CMM) is a model for judging the maturity of the software processes of an organization and for identifying the key practices that are required to increase the maturity of these processes.

Software Testing FAQ

2012-05-22T00:28:00.000-07:00

Manual Testing Interview Question Part-2

27. What is Cause Effect Graph?

A graphical representation of inputs and the associated outputs effects which can be used to design test cases.

28. What is Code Complete?

Phase of development where functionality is implemented in entirety; bug fixes are all that are left. All functions found in the Functional Specifications have been implemented.

29. What is Code Coverage?

An analysis method that determines which parts of the software have been executed (covered) by the test case suite and which parts have not been executed and therefore may require additional attention.

30. What is Code Inspection?

A formal testing technique where the programmer reviews source code with a
group who ask questions analyzing the program logic, analyzing the code with respect to a checklist of historically common programming errors, and analyzing its compliance with coding standards.

31. What is Code Walkthrough?

A formal testing technique where source code is traced by a group with a small set of test cases, while the state of program variables is manually monitored, to analyze the programmer's logic and assumptions.

32. What is Coding?

The generation of source code.

33. What is Compatibility Testing?

Testing whether software is compatible with other elements of a system with which it should operate, e.g. browsers, Operating Systems, or hardware.

34. What is Component?

A minimal software item for which a separate specification is available.

35. What is Component Testing?

Testing of individual software components (Unit Testing).

36. What is Concurrency Testing?

Multi-user testing geared towards determining the effects of accessing the same application code, module or database records. Identifies and measures the level of locking, deadlocking and use of single-threaded code and locking semaphores.

37. What is Conformance Testing?

The process of testing that an implementation conforms to the specification on which it is based. Usually applied to testing conformance to a formal standard.

38. What is Context Driven Testing?

The context-driven school of software testing is flavor of Agile Testing that advocates continuous and creative evaluation of testing opportunities in light of the potential information revealed and the value of that information to the organization right now.

39. What is Conversion Testing?

Testing of programs or procedures used to convert data from existing systems for use in replacement systems.

40. What is Cyclomatic Complexity?

A measure of the logical complexity of an algorithm, used in white-box testing.

41. What is Data Dictionary?

A database that contains definitions of all data items defined during analysis.

42. What is Data Flow Diagram?

A modeling notation that represents a functional decomposition of a system.

43. What is Data Driven Testing?

Testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. A common technique in Automated Testing.

44. What is Debugging?

The process of finding and removing the causes of software failures.

45. What is Defect?

Non-conformance to requirements or functional / program specification

46. What is Dependency Testing?

Examines an application's requirements for pre-existing software, initial states and configuration in order to maintain proper functionality.

47. What is Depth Testing?

A test that exercises a feature of a product in full detail.

48. What is Dynamic Testing?

Testing software through executing it. See also Static Testing.

49. What is Emulator?

A device, computer program, or system that accepts the same inputs and produces the same outputs as a given system.

50. What is Endurance Testing?

Checks for memory leaks or other problems that may occur with prolonged

execution

51. What is End-to-End testing?

Testing a complete application environment in a situation that mimics real-world use, such as interacting with a database, using network communications, or interacting with other hardware, applications, or systems if appropriate.

52. What is Equivalence Class?

A portion of a component's input or output domains for which the component's behaviour is assumed to be the same from the component's specification.

53. What is Equivalence Partitioning?

A test case design technique for a component in which test cases are designed to execute representatives from equivalence classes.

54. What is Exhaustive Testing?

Testing which covers all combinations of input values and preconditions for an element of the software under test.

55. What is Functional Decomposition?

A technique used during planning, analysis and design; creates a functional hierarchy for the software.

Manual Testing Interview Questions

2012-05-22T00:27:00.003-07:00

Manual Testing Interview Questions Part-3

54. What is Functional Specification?

A document that describes in detail the characteristics of the product with regard to its intended features.

55. What is Functional Testing?

Testing the features and operational behavior of a product to ensure they correspond to its specifications. Testing that ignores the internal mechanism of a system or component and focuses solely on the outputs generated in response to selected inputs and execution conditions. or Black Box Testing.

56. What is Glass Box Testing?

A synonym for White Box Testing.

57. What is Gorilla Testing?

Testing one particular module, functionality heavily.

58. What is Gray Box Testing?

A combination of Black Box and White Box testing methodologies? testing a piece of software against its specification but using some knowledge of its internal workings.

59. What is High Order Tests?

Black-box tests conducted once the software has been integrated.

60. What is Independent Test Group (ITG)?

A group of people whose primary responsibility is software testing,

61. What is Inspection?

A group review quality improvement process for written material. It consists of two aspects; product (document itself) improvement and process improvement (of both document production and inspection).

62. What is Integration Testing?

Testing of combined parts of an application to determine if they function together correctly. Usually performed after unit and functional testing. This type of testing is especially relevant to client/server and distributed systems.

63. What is Installation Testing?

Confirms that the application under test recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions.

64. What is Load Testing?

See Performance Testing.

65. What is Localization Testing?

This term refers to making software specifically designed for a specific locality.

66. What is Loop Testing?

A white box testing technique that exercises program loops.

67. What is Metric?

A standard of measurement. Software metrics are the statistics describing the structure or content of a program. A metric should be a real objective measurement of something such as number of bugs per lines of code.

68. What is Monkey Testing?

Testing a system or an Application on the fly, i.e just few tests here and there to ensure the system or an application does not crash out.

69. What is Negative Testing?

Testing aimed at showing software does not work. Also known as "test to fail". See also Positive Testing.

70. What is Path Testing?

Testing in which all paths in the program source code are tested at least once.

71. What is Performance Testing?

Testing conducted to evaluate the compliance of a system or component with specified performance requirements. Often this is performed using an automated test tool to simulate large number of users. Also know as "Load Testing".

72. What is Positive Testing?

Testing aimed at showing software works. Also known as "test to pass". See also Negative Testing.

73. What is Quality Assurance?

All those planned or systematic actions necessary to provide adequate confidence that a product or service is of the type and quality needed and expected by the customer.

74. What is Quality Audit?

A systematic and independent examination to determine whether quality activities and related results comply with planned arrangements and whether these arrangements are implemented effectively and are suitable to achieve objectives.

75. What is Quality Circle?

A group of individuals with related interests that meet at regular intervals to consider problems or other matters related to the quality of outputs of a process and to the correction of problems or to the improvement of quality.

76. What is Quality Control?

The operational techniques and the activities used to fulfill and verify requirements of quality.

77. What is Quality Management?

That aspect of the overall management function that determines and implements the quality policy.

78. What is Quality Policy?

The overall intentions and direction of an organization as regards quality as formally expressed by top management.

79. What is Quality System?

The organizational structure, responsibilities, procedures, processes, and resources for implementing quality management.

80. What is Race Condition?

A cause of concurrency problems. Multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access.

81. What is Ramp Testing?

Continuously raising an input signal until the system breaks down.

82. What is Recovery Testing?

Confirms that the program recovers from expected or unexpected events without loss of data or functionality. Events can include shortage of disk space, unexpected loss of communication, or power out conditions

83. What is Regression Testing?

Retesting a previously tested program following modification to ensure that faults have not been introduced or uncovered as a result of the changes made.

84. What is Release Candidate?

A pre-release version, which contains the desired functionality of the final version, but which needs to be tested for bugs (which ideally should be removed before the final version is released).

85. What is Sanity Testing?

Brief test of major functional elements of a piece of software to determine if its basically operational.

86. What is Scalability Testing?

Performance testing focused on ensuring the application under test gracefully handles increases in work load.

87. What is Security Testing?

Testing which confirms that the program can restrict access to authorized personnel and that the authorized personnel can access the functions available to their security level.

88. What is Smoke Testing?

A quick-and-dirty test that the major functions of a piece of software work. Originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch on fire.

89. What is Soak Testing?

Running a system at high load for a prolonged period of time. For example, running several times more transactions in an entire day (or night) than would be expected in a busy day, to identify and performance problems that appear after a large number of transactions have been executed.

90. What is Software Requirements Specification?

A deliverable that describes all data, functional and behavioral requirements, all constraints, and all validation requirements for software/

91. What is Software Testing?

A set of activities conducted with the intent of finding errors in software.

Manual Testing FAQ

2012-05-22T00:27:00.002-07:00

Manual Testing Interview Questions part-4

92. What is Static Analysis?

Analysis of a program carried out without executing the program.

93. What is Static Analyzer?

A tool that carries out static analysis.

94. What is Static Testing?

Analysis of a program carried out without executing the program.

95. What is Storage Testing?

Testing that verifies the program under test stores data files in the correct directories and that it reserves sufficient space to prevent unexpected termination resulting from lack of space. This is external storage as opposed to internal storage.

96. What is Stress Testing?

Testing conducted to evaluate a system or component at or beyond the limits of its specified requirements to determine the load under which it fails and how. Often this is performance testing using a very high level of simulated load.

97. What is Structural Testing?

Testing based on an analysis of internal workings and structure of a piece of software. See also White Box Testing.

98. What is System Testing?

Testing that attempts to discover defects that are properties of the entire system rather than of its individual components.

99. What is Testability?

The degree to which a system or component facilitates the establishment of test criteria and the performance of tests to determine whether those criteria have been met.

100. What is Testing?

The process of exercising software to verify that it satisfies specified requirements and to detect errors. The process of analyzing a software item to detect the differences between existing and required conditions (that is, bugs), and to evaluate the features of the software item (Ref. IEEE Std 829). The process of operating a system or component under specified conditions, observing or recording the results, and making an evaluation of some aspect of the system or component. What is Test Automation? It is the same as Automated Testing.

101. What is Test Bed?

An execution environment configured for testing. May consist of specific hardware, OS, network topology, configuration of the product under test, other application or system software, etc. The Test Plan for a project should enumerated the test beds(s) to be used.

102. What is Test Case?

Test Case is a commonly used term for a specific test. This is usually the smallest unit of testing. A Test Case will consist of information such as requirements testing, test steps, verification steps, prerequisites, outputs, test environment, etc. A set of inputs, execution preconditions, and expected outcomes developed for a particular objective, such as to exercise a particular program path or to verify compliance with a specific requirement. Test Driven Development? Testing methodology associated with Agile Programming in which every chunk of code is covered by unit tests, which must all pass all the time, in an effort to eliminate unit-level and regression bugs during development. Practitioners of TDD write a lot of tests, i.e. an equal number of lines of test code to the size of the production code.

103. What is Test Driver?

A program or test tool used to execute tests. Also known as a Test Harness.

104. What is Test Environment?

The hardware and software environment in which tests will be run, and any other software with which the software under test interacts when under test including stubs and test drivers.

105. What is Test First Design?

Test-first design is one of the mandatory practices of Extreme Programming (XP).It requires that programmers do not write any production code until they have first written a unit test.

106. What is Test Harness?

A program or test tool used to execute a tests. Also known as a Test Driver.

107. What is Test Plan?

A document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

108. What is Test Procedure?

A document providing detailed instructions for the execution of one or more test cases.

109. What is Test Script?

Commonly used to refer to the instructions for a particular test that will be carried out by an automated test tool.

110. What is Test Specification?

A document specifying the test approach for a software feature or combination or features and the inputs, predicted results and execution conditions for the associated tests.

111. What is Test Suite?

A collection of tests used to validate the behavior of a product. The scope of a Test Suite varies from organization to organization. There may be several Test Suites for a particular product for example. In most cases however a Test Suite is a high level concept, grouping together hundreds or thousands of tests related by what they are intended to test.

112. What is Test Tools?

Computer programs used in the testing of a system, a component of the system, or its documentation.

113. What is Thread Testing?

A variation of top-down testing where the progressive integration of components follows the implementation of subsets of the requirements, as opposed to the integration of components by successively lower levels.

114. What is Top Down Testing?

An approach to integration testing where the component at the top of the component hierarchy is tested first, with lower level components being simulated by stubs. Tested components are then used to test lower level components. The process is repeated until the lowest level components have been tested.

115. What is Total Quality Management?

A company commitment to develop a process that achieves high quality product and customer satisfaction.

116. What is Traceability Matrix?

A document showing the relationship between Test Requirements and Test Cases.

117. What is Usability Testing?

Testing the ease with which users can learn and use a product.

manual Testing FAQ

2012-05-22T00:27:00.001-07:00

Testing FAQ Part-5

118. What is Use Case?

The specification of tests that are conducted from the end-user perspective. Use cases tend to focus on operating software as an end-user would conduct their day-to-day activities.

119. What is Unit Testing?

Testing of individual software components.

120. how do the companies expect the defect reporting to be communicated by the tester to the development team. Can the excel sheet template be used for defect reporting. If so what are the common fields that are to be included ? who assigns the priority and severity of the defect

To report bugs in excel:
Sno. Module Screen/ Section Issue detail Severity
Prioriety Issuestatus
this is how to report bugs in excel sheet and also set filters on the Columns attributes.
But most of the companies use the share point process of reporting bugs In this when the project came for testing a module wise detail of project is inserted to the defect management system they are using. It contains following field
1. Date
2. Issue brief
3. Issue description (used for developer to regenerate the issue)
4. Issue status( active, resolved, on hold, suspend and not able to regenerate)
5. Assign to (Names of members allocated to project)
6. Priority(High, medium and low)
7. Severity (Major, medium and low)

121. How do you plan test automation?

1. Prepare the automation Test plan
2. Identify the scenario
3. Record the scenario
4. Enhance the scripts by inserting check points and Conditional Loops
5. Incorporated Error Handler
6. Debug the script
7. Fix the issue
8. Rerun the script and report the result
122. Does automation replace manual testing?
There can be some functionality which cannot be tested in an automated tool so we may have to do it manually. therefore manual testing can never be replaced. (We can write the scripts for negative testing also but it is hectic task)when we talk about real environment we do negative testing manually.

123. How will you choose a tool for test automation?

choosing of a tool depends on many things ...
1. Application to be tested
2. Test environment
3. Scope and limitation of the tool.
4. Feature of the tool.
5. Cost of the tool.
6. Whether the tool is compatible with your application which means tool should be able to interact with your application
7. Ease of use

124. How you will evaluate the tool for test automation?

We need to concentrate on the features of the tools and how this could be beneficial for our project. The additional new features and the enhancements of the features will also help.

125. How you will describe testing activities?

Testing activities start from the elaboration phase. The various testing activities are preparing the test plan, Preparing test cases, Execute the test case, Log teh bug, validate the bug & take appropriate action for the bug, Automate the test cases.

126. What testing activities you may want to automate?

Automate all the high priority test cases which needs to be executed as a part of regression testing for each build cycle.

127. Describe common problems of test automation.

The common problems are:
1. Maintenance of the old script when there is a feature change or enhancement
2. The change in technology of the application will affect the old scripts
128. What types of scripting techniques for test automation do you know?
5 types of scripting techniques:
Linear
Structured
Shared
Data Driven
Key Driven

129. What is memory leaks and buffer overflows ?

Memory leaks means incomplete deallocation - are bugs that happen very often. Buffer overflow means data sent as input to the server that overflows the boundaries of the input area, thus causing the server to misbehave. Buffer overflows can be used.

130. What are the major differences between stress testing,load testing,Volume testing?

Stress testing means increasing the load ,and checking the performance at each level. Load testing means at a time giving more load by the expectation and checking the performance at that level. Volume testing means first we have to apply initial.

Usability Testing

2012-05-20T22:56:00.000-07:00

Software Usability Testing

What is Usability Testing?

Usability testing is a test type to ensure that the intended users of a system or Application can carry out the intended tasks efficiently, effectively and satisfactorily.

When is Usability Testing appropriate?

Usability testing it is carried out pre-release so that any significant issues identified can be addressed. Usability testing can be carried out at various stages of the design process. In the early stages, however, techniques such as walkthroughs are often more appropriate.
Usability testing is not a substitute for a human-centred design process.

Who should attend?

A usability testing session should be attended by:
• A representative user
• A test host.

It is highly recommended to also have in attendance as observers:

• At least 1 developer.
• At least 1 business representative.
Observers should ideally be in a separate
observation room.

How many test sessions should be conducted?
This depends on the complexity of the system, the number of intended users, and budgetary constraints. Even one test session is better than
none, but 6 to 8 will tend to uncover the majority of significant issues.

How to prepare for Usability testing:

• Identify representative tasks. Ideally, these should derive from scenarios or use cases developed earlier in the design process. Have a clear definition of when a task is complete.

• Prepare a test schedule.
• Book the required room/s.
• Identify representative users and invite them to attend.

We will need the following materials:

• A formal script so that all participants are treated in the same way.
• A consent form for video-taping (if conducted).
• A pre-evaluation questionnaire to check that your participants match the required profile, and to check whether any effects observed are dependent on demographic attributes.
• A list of tasks, together with criteria for measuring whether they have been successfully completed.
• Logging sheets to record timing, events, participant actions, concerns and comments.
• A post-evaluation questionnaire to measure user satisfaction and understanding and to glean any additional information participants
may want to provide.
• Cash or an appropriate 'thank-you' gift.

Guidelines

• For all but the simplest and most informal tests, run a pilot test first.
• Ensure participants are put at ease, and are fully informed of any taping or observation. Attend at least one test as a participant, to
appreciate the stress that participants undergo.
• Ensure that participants have the option to abandon any tasks which they are unable to complete.
• Do not prompt participants unless it is clearly necessary to do so.
• Record events in as much detail as possible— to the level of keystrokes and mouse clicks if necessary.
• If there are observers, ensure that they do not interrupt in any way. Brief observers formally prior to the test.
• Be sensitive to the fact that developers may be upset by what they observe or what you report.

Goals of usability testing

Usability testing is a black-box testing technique. The aim is to observe people using the product to discover errors and areas of improvement. Usability testing generally involves measuring how well test subjects respond in four areas: efficiency, accuracy, recall, and emotional response. The results of the first test can be treated as a baseline or control measurement; all subsequent tests can then be compared to the baseline to indicate improvement.

    Performance: How much time, and how many steps, are required for people to complete basic tasks? (For example, find something to buy, create a new account, and order the item.)

    Accuracy: How many mistakes did people make? (And were they fatal or recoverable with the right information?)

    Recall: How much does the person remember afterwards or after periods of non-use?

    Stickiness: How much time he/she spends

    Emotional response: How does the person feel about the tasks completed? Is the person confident, stressed? Would the user recommend this system to a friend?

To assess the usability of the system under usability testing, quantitative and/or qualitative Usability goals (also called usability requirements have to be defined beforehand. If the results of the usability testing meet the Usability goals, the system can be considered as usable for the end-users whose representatives have tested it.

VBScript Variables

2012-05-18T21:40:00.005-07:00

VBScript Variables (New Version Document)

Variables

Chapter Index

a) What is Variable?

b) How to declare Variables in VBScript?

c) Implicit & Explicit Declaration of Variables

d) Option Explicit Statement

e) Assigning values to Variables

f) Purpose of Variables

g) Naming Restrictions

h) Scope of Variables

i) Types Variables

j) Array Variables

k) Dynamic Arrays, Dimensional Arrays

l) Assigning series values to Array Variables
------------------------------------------------------------------

a) What is Variable?

Definition 1:
A variable is a convenient placeholder that refers to a computer memory location where we can store program information that may change during the time our script is running.

Definition 2:
A named memory Location for storing the Data.

Variables store in Primary Memory (RAM)

Primary Memory: RAM

Secondary Memory: HDD, CD ROM, USB etc...

b) How to declare Variables in vbscript?

We can use either Public or Private or Dim Statements for declaring variables.

Generally we use Dim Statement for declaring variables.

Example:

Dim a
Dim b
Dim c
-----------

Dim a, b, c

Note: We can declare multiple variables in a statement by separating with comas, otherwise we can use multiple statements.

c) Implicit & Explicit Declaration of Variables

VBScript supports Implicit and Explicit declaration of variables, but declaring variables explicitly is the best practice.

Dim num1

num1 = 100 'Explicit variable

num2 = 200 'Implicit variable

Msgbox "Addition of num1, num2 is: "&num1+num2

In the above example num1 is Explicit variable, first we declared then used.

num2 is Implicit variable, we used num2 without declaration.

-------------------------------------------------

d) Option Explicit Statement

Option Explicit statement forces declaration of all variables in the Script, and it should be the first statement. Using this statement we can avoid misspell problems.

Ex:
-----

Option Explicit

Dim Tickets, Price, Total

Tickets = 5

Price = 120

Total = Tickets * Priee

Msgbox Total

-----------------------------------------------

e) Assigning values to Variables

In Computer programming value assignment is 2 types:

1) Initialization
Assigning values directly in the Script / Program

2) Reading
Reading from Input devices, from files, from Databases, and Reading from Application Objects.

Example:

Dim num1, num2

num1 = 100 'Initialization

num2 = InputBox("Enter num2") 'Reading

Msgbox num1 + num2

---------------------

f) Purpose of Variables

1) 'Holding the data
------------------------
Dim a, b, c

a= 100 'Holding the data

a = 10

b=3

2) 'Store the value that returned by a program
--------------------------------------------------------

c = a ^ b 'Store the value that returned by a program

Msgbox c '1000

3) 'Store the value that returned by a Function
------------------------------------------------------

c= Date 'Store the value that returned by a Function

Msgbox c

4) 'Storing Object Reference
---------------------------------

Set a = CreateObject("Scripting.FileSystemObject") 'Storing Object Reference

5) Passing as Parameter
----------------------------------
Dim orderNo

For orderNo = 1 to 5 Step 1

        Window("Flight Reservation").Activate

        Window("Flight Reservation").WinButton("Button").Click

        Window("Flight Reservation").Dialog("Open Order").WinCheckBox("Order No.").Set "ON"

        Window("Flight Reservation").Dialog("Open Order").WinEdit("Edit").Set orderNo

        wait 2

        Window("Flight Reservation").Dialog("Open Order").WinButton("OK").Click

Next

g) Naming Restrictions

a) Should start with Alfa bytes

Dim abc 'Correct

Dim a9 ' Correct

Dim ab c 'Incorrect

Dim 9ab 'Incorrct

b) Should not contain embedded periods

Dim abc 'Correct

Dim ab c 'Incorrect

Dim ab-c 'Incorrect

Dim ab*c 'Incorrect

Dim ab.c 'Incorrect

Dim ab_c 'Correct

c) Must not exceed 255 char in length

d) Must be unique in the scope of declaration

Dim a, b, c

Dim d, e, f

Dim g, h, A 'Incorrect

--------------------------

Don't use Reserved words

Dim Wait

Wait =100

Msgbox Wait

----------------------------------

h) Scope of Variables

-------------------

a) Program / Script Level Variables

b) Function / Procedure Level Variables

Script Level Variables can be used for entire script, whereas Function level variables can be used within the Function only.

Example:

Dim a, b, c 'Script Level

a= 10

b=20

c= a +b

Msgbox c 'Output 30

Function xyz()

   Dim d, e 'Function Level

   d=40

   e= a + d

   Msgbox e 'Output 50

End Function

Call xyz()

Dim f, g 'Script Level

f= 70

g= b + d + f '(20 + 0 +70)

Msgbox g '90

-----------------------------

Option Explicit

Dim a, b, c 'Script Level

a= 10

b=20

c= a +b

Msgbox c '30

Function xyz()

   Dim d, e 'Function Level

   d=40

   e= a + d

   Msgbox e '50

End Function

Call xyz()

Dim f, g 'Script Level

f= 70

g= b + d + f

Msgbox g 'Error

------------------------------------------

i) Types Variables

a) Scalar Variables -for holding one value at a time

b) Array Variables - for holding series of values at a time based on size of the Array

j) Array Variables

Dim a, b(3)

b(0) = "India"

b(1) =100

b(2) =10.234

b(3) =40

a = b(1) + b(3)

Msgbox a '140

--------------------

Dim a, b(3)

b(0) = "India"

b(1) =100

b(2) =10.234

b(3) =40

b(4) = 50 'Error

a = b(1) + b(3)

Msgbox a '140

k) Dynamic Arrays, Dimensional Arrays

Dim a, b(3), c()

ReDim c(3)

c(0) =10

c(1) =20

c(2) =30

c(3) =40

a= c(1) + c(3)

Msgbox a '60

ReDim c(5)

c(4) = 50

c(5) = 60

a= c(2) + c(5)

Msgbox a '60

Preserve Keyword
If we use preserve keyword it carry's existing data as it is.
----------------

Dim a, b(3), c()

ReDim c(3)

c(0) =10

c(1) =20

c(2) =30

c(3) =40

a= c(1) + c(3)

Msgbox a '60

ReDim Preserve c(5)

c(4) = 50

c(5) = 60

a= c(2) + c(5)

Msgbox a '90

----------------------

Dim a, b(3), c(), d(4, 5)

d(0, 0) ="QTP"

l) Assigning series values to Array Variables

a) Using Array Function

Dim a

Msgbox IsArray(a) 'False

a = Array("India",100, 100.34, #10/10/2010#)

Msgbox IsArray(a) 'True

Msgbox a(1) '100

b) Using Split Function

Dim a, b

a= "VB@Script@Language"

Msgbox IsArray(b) 'False

b= Split(a,"@")

Msgbox IsArray(b) 'True

Msgbox b(1) 'Script

Dim a, b

a= "VB Script Language"

Msgbox IsArray(b) 'False

b= Split(a)

Msgbox IsArray(b) 'True

Msgbox b(1) 'Script
-----------------------------------------------
Note: In Perl script 3 types of variables available, 1) Scalar Variables, 2) Array Variables, 3) Associated Arrays, but in VBScript 2 types variables only.

VBScript Provided Dictionary Object, it is equivalent to Associated Array in Perl Script
-----------------------------------------------------------------------------------------

VBScript Variables FAQ Link

QTP Tool Menus

2012-05-18T21:40:00.003-07:00

QTP Tool Window Menus

QTP Tool Menus

QTP has 10 Menus (File, Edit, View, Insert, Automation, Resources, Debug, Tools, Windows, and Help)

a) File Menu
-------------

New Test

Open Existing Test

Save Test default location (D:\Program Files\HP\QuickTest Professional\Tests)

Save Test in diff location

Save Test With Resources

Save Test in QC / ALM Project

Close Test

Print Test

Export Test to ZIP format

Import Test from ZIP

Settings
    Associate Library files
    Environment Variable files
    Recovery scenario files

Exit
-------------------------------------------------
2) Edit Menu
---------------
a) Editor Commands
Redo,
Undo,
Cut,
Copy,
Paste,
delete,
Find,
Replace
etc...

b) Action Commands

Split Action
Delete Action
Rename Action
Action Properties
    Make Reusable to Non-Reusable and vice versa
    Action Parameter (Input, Output)
-------------------------------------------
3) View Menu
-------------
Active screen,

Data table

Information

Debug viewer

Missing resources

Test Flow
------------------------
4) Insert Menu
---------------
Checkpoints

Output values

Flow Control statements
    Conditional
    Loop
Synchronization point

Transaction points

Step Generator

b) Action Commands

Create New Action

Call Action

Copy Action

--------------
*** Call WinRunner Test
    WinRunner Function

5) Automation
-------------
Record,
Run,
Stop
Analog Recording
Low Level Recording
Record & Run Setting
View Results

6) Resources
----------------
a) Object Repository Commands

Launch Local Repository

Edit Local Objects

Create Shared objects

Edit Shared objects

Associate Shared object Repositories

b) Recover Scenario Commands

Create New Recover Scenarios

Edit Recover Scenarios

View and Edit Associated Library files

7) Debug Menu:
---------------
Step into (F11)

Step Over (F10)

Step Out (Shift + F11)

Breakpoint (F9)

8) Tools Menu
-----------------
Options,

View Options,

Object Identification

Object Spy

Virtual Object

Data Driver

Regular Expression Evaluator *** Added in 11.00 V

9) Windows
----------
Styles of presentation

10) Help
----------
QTP Tool features documentation

VBScript documentation

Check for updates

Knowledge base

Raise Tickets to vendor

Product Info

Version Info

Manual Testing Training

2012-05-15T07:32:00.001-07:00

Manual Testing Training

Program will commence on:

Timings: 5:30 PM to 7:00 PM (Indian Standard Time)

8:00 AM to 9:30 AM (EST)

7:00 AM to 8:30 AM (CST)

5:00 AM to 6:30 AM (PST)

Fee: 125 US Dollars

Duration: 20 Hours

Contact: gcreddy@gcreddy.com

-------------------------------------

Software Testing Syllabus

I) Introduction

a)    Software, Types of Software
b)    Software Project, Application and Product
c)    Software Business Process

II) SDLC

a)    Requirements Gathering
b)    Analysis & Planning
c)    Software Design
d)    Coding/Implementation
e)    Testing
f)    Release & Maintenance

III) SDLC Models

a)    Sequential Models
        1)    Waterfall Model
        2)    ‘V’ Model
b)    Incremental / Iterative Models
       1)    Prototype Model
       2)    Spiral Model
       3)    Agile Model

IV) Test Levels

a)    Unit Testing/Component Testing/Module Testing / Program Testing
b)    Integration Testing
c)    System Testing
d)    Acceptance Testing

V) Software Environment

a)    I-Tier or Standalone Applications
b)    II-Tier or Client/Server Applications
c)    III-Tier or Web Applications
d)    N-Tier or Distributed Applications

VI) Test Types

a)    Functional Testing
b)    Non-Functional Testing
c)    Structural Testing
d)    Re & Regression Testing

VII) Test Design Techniques

a)    Black box Techniques
1)    Equivalence Partitioning/ Equivalence Classes (EP/EC)
2)    Boundary Value Analysis (BVA)
3)    Decision Table Testing
4)    State Transition Testing
5)    Use Case Testing
b)    White box Techniques
1)    Statement Testing
2)    Decision Testing
3)    Condition/Multi Condition Testing
4)    Mutation Testing

VIII) Testing Process (STLC)

a)    Test Strategy
b)    Test Planning
c)    Configuration Management
d)    Risk Analysis
e)    Test Design (Test Scenarios, Test Cases and Test Data)
f)    Test Execution
g)    Defect Reporting & Tracking
h)    Status Reporting
i)    Test Closure

IX) Informal Testing

a) Exploratory Testing
b) Error Guessing
------------------------------------------------------------

X) Quality Standards

a)    ISO Standards
b)    IEEE Standards
c)    CMM/CMM (I) Process Guidelines

XI) Software Business Domains

a)    BFSI
b)    ERP
c)    Healthcare
d)    Telecom
e)    Ecommerce
f)    Others

introduction to c

2012-05-11T22:05:00.002-07:00

C Programming Language Introduction

C Language is a powerful programming language developed by Denis Ritche in 1972. C Language is a general purpose language but normally used for system programming.

C is a High Level Programming Language, Compiler is required in order to convert the high level language (English like) into machine level language (Binary Language).

As a programming language, C is rather like Pascal or Fortran. Values are stored in variables. Programs are structured by defining and calling functions. Program flow is controlled using loops, if statements and function calls. Input and output can be directed to the terminal or to files. Related data can be stored together in arrays or structures.

C allows the most precise control of input and output. C is also rather more terse than Fortran or Pascal. This can result in short efficient programs, where the programmer has made wise use of C's range of powerful operators. It also allows the programmer to produce programs which are impossible to understand.

Programmers who are familiar with the use of pointers (or indirect addressing, to use the correct term) will welcome the ease of use compared with some other languages. Undisciplined use of pointers can lead to errors which are very hard to trace. This course only deals with the simplest applications of pointers.

It is hoped that newcomers will find C a useful and friendly language. Care must be taken in using C. Many of the extra facilities which it offers can lead to extra types of programming error. You will have to learn to deal with these to successfully make the transition to being a C programmer.

Advantages of C

    Easy to learn

    Structured language

    It produces efficient programs.

    It can handle low-level activities.

    It can be compiled on a variety of computers.

It has huge knowledge base

Purpose of C Language

C was initially used for system development work, in particular the programs that make-up the operating system. C was adopted as a system development language because it produces code that runs nearly as fast as code written in assembly language. Some examples of the use of C might be:

    Operating Systems
    Language Compilers
    Assemblers
    Text Editors
    Print Spoolers
    Network Drivers
    Modern Programs
    Databases
    Language Interpreters
    Utilities
    Application development
    Embedded Systems
    Test Automation etc...

C Data Types

2012-05-11T22:05:00.001-07:00

Data Types in C

What is Data Type?

In Computer programming, classification of a particular type of information is called Data Type. It helps humans to differentiate the information.

C Language supports explicit declaration of ‘data types' which are used to define a variable before its use.

Data Types Available in C Language

char

int

float

double

void

enum

There is not a Boolean data type, C does not have the traditional view about logical comparison.

Recent C++ compilers do have a Boolean data type.

char - data type

char defines characters.

{

char Letter;

Letter = 'gcreddy';

}

int - data type

int is used to define integer numbers.

{

int Count;

Count = 123;

}

float - data type

float is used to define floating point numbers.

{

float Miles;

Miles = 1.34;

}

double - data type

double is used to define BIG floating point numbers. It reserves twice the storage for the number. On PCs this is likely to be 8 bytes.

{

double Atoms;

Atoms = 2500000;

}

Modifiers

The three data types above have the following modifiers.

short

long

signed

unsigned

The modifiers define the amount of storage allocated to the variable. The amount of storage allocated is not cast in stone. ANSI has the following rules:

short int <= int <= long int

float <= double <= long double

What this means is that a 'short int' should assign less than or the same amount of storage as an 'int' and the 'int' should be less or the same bytes than a 'long int'. What this means in the real world is:

Data Type	Range	Bytes
short int	-32,768 to +32,767	2
unsigned short int	0 to +65,535	2
unsigned int	0 to +4,294,967,295	4
int	-2,147,483,648 to +2,147,483,647	4
long int	-2,147,483,648 to +2,147,483,647	4
single char	-128 to +127	1
unsigned char	0 to +255	1
float		4
double		8
long double		12

These figures only apply to todays generation of PCs. Mainframes and midrange machines could use different figures, but would still comply with the rule above.

We can find out how much storage is allocated to a data type by using the size of operator.

Qualifiers

const

volatile

The const qualifier is used to tell C that the variable value can not change after initialisation.

const float pi=3.14159;

pi cannot be changed at a later time within the program.

Another way to define constants is with the #define preprocessor which has the advantage that it does not use any storage.

sdlc models

2012-05-09T21:21:00.004-07:00

Software Development Life Cycle Models Interview Questions

1) What is the difference between SDLC and STLC?

STLC or Software Test Process is a part of SDLC

Software Development Life Cycle involves the complete Verification and Validation of a Process or a Project.

Whereas Software Testing Life Cycle involves only in Validation.

STLC or Software Test Process is a part of SDLC

Software Development Life Cycle involves

a) Requirements Gathering and Base line

b) Analysis & Planning

c) Software Design (High level & Low Level)

d) Coding / Implementation

e) Testing

f) Release & Maintenance

Where as Software Testing Life cycle involves.

a) Test Planning
b) Test Analysis & Design
c) Test Implementation & Execution
d) Evaluating exit criteria
e) Test Closure

2) What are the different software development models?

a) Waterfall model

b) V Model

c) Prototype Model

d) Spiral Model

e) Agile Models

f) RUP (Rational Unified Process)
Etc...

3) Why Software Development Life Cycle Model is important to develop Software Application?

It is a systematic approach to develop software Application, we follow SDLC Models in order to improve the Quality.

4) What is Waterfall Model?

Waterfall Model is one of the most widely used Software Development Process. It is also called as Linear Sequential model. It is widely used in the commercial development projects . It is called so because here, we move to next phase(step) after getting input from previous phase, like in a waterfall, water flows down to from the upper steps.

database testing faq

2012-05-09T21:21:00.003-07:00

Database Testing Interview Questions

1) What is Database testing?

Database testing basically include the following.
1)Data validity testing.
2)Data Integrity testing
3)Performance related to database.
4)Testing of Procedure, triggers and functions.

for doing data validity testing you should be good in SQL queries
For data integrity testing you should know about referential integrity and different constraint.
For performance related things you should have idea about the table structure and design. For testing Procedure triggers and functions you should be able to understand the same.

2) What we normally check for in the Database Testing?

In DB testing we need to check for,
1. The field size validation
2. Check constraints.
3. Indexes are done or not (for performance related issues)
4. Stored procedures
5. The field size defined in the application is matching with that in the db.

3) How to Test database in manually? Explain with an example
Observing that operations, which are operated on front-end is effected on back-end or not.

The approach is as follows:
While adding a record thru' front-end check back-end that addition of record is effected or not. So same for delete, update,...... Ex:Enter employee record in database thru' front-end and check if the record is added or not to the back-end(manually

manual testing interview questions

2012-05-09T21:21:00.002-07:00

Software Testing FAQ

Click on below Links for Interview Questions

QA:It is process oriented
      it involves in entire process of software development.
      Prevention oriented.
QC:
     It is product oriented.
     work to examine the quality of the product.
     Detection oriented.

2) what is a bug?

Mismatch in Software Application

3.what is a test case?

Testcase is set of input values, execution preconditions,expected results and execution post conditions, developed for a particular objective or test conditons, such as to exercise a paticular program path or to verify compliance with a specific requiremnt.

4) What is the purpose of test plan?

Test plan document is prepared by the test lead or team lead,it contains the contents like introduction,objectives,test strategy,scope,test items,program modules user procedures,features to be tested features not to tested approach,pass or fail criteria,testing process,test deliverables, testing, tasks, responsibilities,resources,schedule, environmental requirements, risks & contingencies,change management procedures,plan approvals,etc all these things help a test manager understand the testing he should do &
what he should follow for testing that particular project.

5) what is basis for testcase review?

the main basis for the test case review is
1.testing techniques oriented review
2.requirements oriented review
3.defects oriented review.

6)what are the contents of SRS documents?

System requirements specifications and Functional requirements specifications.

7)what is Regression testing?

After the Bug fixed ,testing the application whether the fixed bug is affecting remaining functionality of the application or not.Majorly in regression testing Bug fixed module and it's
connected modules are checked for thier integrity after bug fixation.

8) what is build duration?

it is a tine gap between old version build and new version build in new version build some new extra features are added

9) What is test deliverables?

Test deliverables are nothing but documents preparing during testing like test plan document test case docs bug reports etc..

Test deliverables will be delivered to the client not only for the completed activities ,but also for the activities, which we are implementing for the better productivity.(As per the company's standards)

1.QA Test Plan
2.Test case Docs
3.QA Test plan,

if we are using Automation.
4.Automation scripts
5.QA Coverage Matrix and defect matrix.
6.Traceability Matrix
7.Test Results doc
8.QA Schedule doc(describes the deadlines)
9.Test Report or Project Closure Report.(Prepared once we rolled out the project to client)
10.Weekly status report(sent by PM to the client)
11.Release Notes.

10) If a project is long term project , requirements are also changes then test plan will change or not? why?

Yes..definitely. If requirements change, the design documents, specifications (for that particualr module which implements the requiremnts) will also change. Hence the test plan would also need to be updated.

Test Item Transmittal Report

2012-05-02T21:19:00.000-07:00

Test Item Transmittal Report

Purpose

To identify the test items being transmitted for testing. It includes the person responsible for each item, its physical location, and its status. Any variations from the current item requirements and designs are noted in this report.

Outline

A test-item transmittal report shall have the following structure:

    Transmittal-report identifier
    Transmitted items
    Location
    Status
    Approvals

The sections shall be ordered in the specified sequence. Additional sections may be included just prior to Approvals. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content. The referenced material must be attached to the test-item transmittal report or available to users of the transmittal report.

Details on the content of each section are contained in the following sections.

Cover Page

No cover page is required for this document.

Section Description
Transmittal-Report Identifier

Specify the unique identifier assigned to this test item transmittal report.

Transmitted Items

Identify the test items being transmitted, including their version/revision level. Supply references to the item documentation and the test plan relating to the transmitted items. Indicate the people responsible for the transmitted items.

Location

Identify the location of the transmitted items. Identify the media that contain the items being transmitted. When appropriate, indicate how specific media are labeled or identified.

Status
Describe the status of the test items being transmitted. Include deviations from the item documentation, from previous transmittals of these items, and from the test plan. List the incident reports which are expected to be resolved by the transmitted items. Indicate if there are pending modifications to item documentation which may affect the items listed in this transmittal report.

Approvals

Specify the names and titles of all persons who must approve this transmittal. Provide space for the signatures and dates.

test log

2012-05-02T21:18:00.005-07:00

Test Log Template (IEEE 829-1998)

Test Log Identifier

Some type of unique company generated number to identify this test log, its level and the level of software that it is related to. Preferably the test log level will be the same as the related test case or procedure level. Ideally the test log naming convention should follow the same general rules as the testware it is related to. This is to assist in coordinating software and testware versions within configuration management.

Unique "short" name for the Log
Version Date and Version Number of Log

Description

Items being tested and any supporting reference materials

Case Specification
Procedure specification
Transmittal report

Date & time
Executed by

Tester
Observer

Environment

Especially any variances from the planned test environment

Activity and Event Entries

Date/Time

Beginning of each significant activity
End of each activity

Execution description

Procedure executed (reference to its location)
Personnel present at test

Tester, developer, observer
Reason for each persons presence

Procedure Results

For each execution, log all relevant information

Error messages, aborts, interventions
Location of outputs

Result status (success, failure, unknown)

Environmental Information

Any changes or substitutions from requested environment

Anomalous Events

Record events before and after an anomaly
Any special situations

Power interruptions, etc.

Incident reports

Report on each unexpected result or variance from expected output

test incident report

2012-05-02T21:18:00.004-07:00

Test Incident Report

Purpose

To document any event that occurs during the testing process which requires investigation.

Outline

A test-incident report shall have the following structure:

    Test-incident-report identifier
    Summary
    Incident description
    Impact

The sections shall be ordered in the specified sequence. Additional sections may be included at the end. If some or all of the content of a section is in another document, then a reference to that material may be listed in place of the corresponding content. The referenced material must be attached to the test incident report or available to users of the incident report.

Details on the content of each section are contained in the following sections.

Cover Page

No cover page is required for this document.

Section Description

Test-Incident-Report Identifier
Specify the unique identifier assigned to this test incident report.

Summary

Summarize the incident. Identify the test items involved indicating their version/revision level. References to the appropriate test-procedure specification, test-case specification, and test log should be supplied.

Incident Description

Provide a description of the incident. This description should include the following items:

    Inputs
    Expected results
    Actual results
    Anomalies
    Date and time
    Procedure step
    Environment
    Attempts to repeat
    Testers
    Observers

Related activities and observations that may help to isolate and correct the cause of the incident should be included. For example, describe any test-case executions that might have a bearing on this particular incident and any variations from the published test procedure.

Impact

If known, indicate what impact this incident will have on test plans, test design specifications, test-procedure specifications, or test-case specifications.

test summary report

2012-05-02T21:18:00.003-07:00

IEEE Test Summary Report

IEEE Test Summary Report Identifier

Some type of unique company generated number to identify this summary report, its level and the level of software that it is related to. Preferably the report level will be the same as the related software level. The number may also identify whether the summary report is for the entire project or a specific level of testing. This is to assist in coordinating software and testware versions within configuration management.

Summary

Identify all relevant support materials so that the reader of the report knows which version and release of the project/software is being reported on. It may be particularly important to identify the specific version of an external package used in the testing, especially if a new release occurred during the test cycle and was not included. The version/release information should
match the information contained in the configuration management system and may include the following elements.

· Test Items – This should match the item definitions from the appropriate level test plan that this report is covering. Any variance from the items specified in the test plan should be identified. Elements from the features sections of the test plan (both included and excluded) can also be included here or in a separate reference section.

· Environment – The environment and any variances for that identified in the test plan should be verified here to ensure that the correct test set-up was used. This will help avoid confusion when the product is released to production and will ensure that the test environment matches the destination platform.

· References – Any documents that support this report and their location within the configuration management system.

Variances

Document any changes or deviations from those areas agreed on in the reference documents, especially in areas that may cause concern to the group accepting the test results. Include references to any supporting documentation that covers the reasons for the deviations.

· From Test Plans or Specifications

· Reasons for Deviations

· Support materials and documents
      · Change requests
      · Enhancement requests
      · Incident reports (incident left in by intent)

Comprehensiveness Assessment

Evaluation of the testing and test process in terms of the documented test objectives. This is to assess the quality and effectiveness of testing so that assessment of the software can be viewed correctly. Keep in mind that a coverage assessment only has meaning in relation to a known set of initial test objectives.

Cover how effective testing was, and any weaknesses in the process, especially any surprising trends and the causes of those deviations.

· Evaluation of test coverage
       · Total objectives (by Inventory category)
       · Objectives covered (depth and width)
       · Objectives omitted and reason for omission

· Identification of uncovered attributes
       · Surprising trends and test process changes to cover them

Summary of Results

Report on the overall status of the incidents. Focus should be on trends and patterns in the process and not on specific individuals or teams. Avoid pure numbers, as numbers due not really provide insight as to the nature and cause of problems. The focus should be on costs, impacts, and trends; including any positive trends. This is where you begin to set the stage for the
evaluation of the test process, the quality of the testing and the software quality and can include
areas such as:

· Total Incidents
· By Severity and Priority
· By cost/failure impact
· Defect Patterns
· Open or Unresolved incidents

Evaluation

Based on the evaluation of the testing as documented in sections three (3) through (6) assess the quality of the software. This should be an objective assessment of the failure likelihood and overall quality in terms of the criteria specified in the appropriate level test plan. Each item identified in Section 2 under test items should be covered in the evaluation.

Include Good news as well. If the application tested out with high quality in some areas (even though others were no so good) be sure to state that as well.

· Limitations
       · Incomplete or partial functions/features
       · Dropped features (due to requirements change or defects)
· Failure Likelihood
       · High or Medium risk areas
       · Good quality areas or features

Summary of Activities

Cover the planned activities and the changes to those plans especially in areas where the amount of actual effort greatly exceeded the planned effort. Include the reasons for the variances and the possible impact on the testing staff. Major impacts to the testing staff will have possible negative effects on follow-on projects or on the next project in line.

· Staff time used
        · Hours per day/week
· Elapsed time versus staff time
        · Is staff working excess hours per week
· Costs – planned versus actual
· Variances and the reasons for the change
        · Changes to the project scope and direction
        · Requirements and design changes
        · Surprising defect trends
        · Loss of personnel (development, test, etc.)
        · Test environment availability and accuracy

Approvals
Provide a list and signature block for each approving authority. This should match the list of names that approved the test plan in the first place. Those who agreed to the test plan need to verify the results of the testing.

Test Procedure

2012-05-01T23:28:00.005-07:00

Test Procedure Specification Template

Test Procedure Specification Identifier

Some type of unique company generated number to identify this test procedure specification, its level and the level of software that it is related to. Preferably the procedure specification level will be the same as the related software level. Ideally the procedure naming convention should follow the same general rules as the software it is related to. This is to assist in coordinating software and testware versions within configuration management.

· Unique "short" name for the procedure

· Version date and version number of procedure

· Version Author and contact information

· Revision history

Purpose

· List all test cases covered by the procedure

· Description of the procedure

Special Requirements

· Manual or Automated

· Stages in which test is to be used (pre-testing, repair and regression testing, future compliance testing, end-to-end testing, re-testing after certification, etc.)

· Test environment

· Special skills or training required (especially if automated)

· Any prerequisite procedures

Steps

What are the activities associated with the procedure. Include any of the following activities that may be required to execute the procedure.

· Log

· Set-up

· Start

· Proceed

· Measure

· Shutdown

· Restart

· Stop

· Wrap-up

· Contingencies