Qualities of a Manual Test Engineer Even with test automation, the manual test engineer remains a key role. Manual test engineer is trained in the test tools so that he can run the automated scripts generated by other team members. This helps a single person or group to run all the tests and verify the results from both the manual and automated tests. Responsibilities of a Manual Test Engineer are 1) Analyzing the project risk & identification of the project requirements 2) Development of documentation to design the overall testing scenarios, and describing the test data requirements to achieve the…

Download Link for your Favorite E-Book is at the End of this Page *********************************************************************************** Discover the Power of LoadRunner for Performance Testing Prior to understanding the LoadRunner as a performance-testing tool, let us understand a few basics of the Performance Testing as such. Performance Testing is the process of testing and fine tuning the software application in line with the intent of realizing the desired performance. Performance Testing is a part of Performance Engineering Domain. It covers commonly referred term load or spike or stress testing and validating the system performance. Usually there are Three main Categories of Performance like: Speed – Is…

Download Link for your Favorite Presentation is at the End of this Page ****************************************************************************************** Difference between STLC and SDLC STLC means “Software Testing Life Cycle”. It involves following stages 1) Preparation of the test strategy 2) Preparation of the test plan 3) Creation of the test environment 4) Writing of the test cases 5) Creation of the test scripts 6) Execution of the test scripts 7) Analysis of the test results 8) Reporting of the bugs 9) Performing regression testing SDLC means “Software or System Development Life Cycle”. It involves following stages 1) Initiation of the Project 2) Collection of Requirements and…

Pros and Cons of Automated Testing Introduction to Automated testing: “Automated Testing” means automating the manual testing process currently in use. The prime requirement is of presence of a formalized “manual testing process” in the organization. Automation refers to the use of strategies & tools which augment or reduce the need of manual or human involvement in unskilled, repetitive or redundant tasks. Automation process includes � Creation of detailed test cases, including predictable “expected results”, which have been derived from Business Functional Specifications and other Design documentation. A standalone Test Environment, including a Test Database that is restorable to a…

Understand the Best Practices in Test Automation Why Automated Testing is Needed?: Today, rigorous application testing is a critical part of virtually all software development projects. As more organizations develop mission � critical systems to support their business activities, the need is greatly increased for testing methods that support business objectives. It is necessary to ensure that these systems are reliable, built according to specification and have the ability to support business processes. Many internal and external factors are forcing organizations to ensure a high level of software quality and reliability. Why Automate the Software Testing Process?: In the past, most software…

Art of Writing an effective Description of a Bug A Software Bug can be described through detailed explanation of the unexpected behavior happening as a result of some action performed on the software application. 1) Be specific writing the description of the Bug. Describe the behavior, which was expected, but did not happen. Describe as to what happened instead. For example the window closed as against appearing of the pop-up. 2) Description should be in the present tense. 3) Description should not have unnecessary words. 4) Description should not have exclamation points. 5) Always finish the sentences with a period. 6)…

Nine Tips for an Effective Bug Reporting It is important that a software tester reports everything what he feels. A software tester role is that of a catalyst in any team. He makes up the team on one hand and breaks up the application on the other. It is important to clearly understand all the issues in the application may be big or small with due course of understanding in terms of business and the application. Therefore a strong Bug Report serves as a definite proof in Software Development Life Cycle, provided the status of bugs is updated at all…

Mastering the Art of Effective Bug Reporting All software testers strive to achieve the prime aim of hunting maximum number of bugs in the software. When some build gets ready for testing, the main aim of the tester is to dig out maximum possible bugs from each & every corner. To achieve perfection in this task testing is performed from different angles. The application under test is subjected to the rigors of the following type: # Boundary value analysis # Validation Testing # Verification Testing # GUI Testing # Interoperability Testing # Integration Testing # Functional Testing  from Business concept…

How Severe your Bug is It is extremely important to understand the type & importance of every bug detected during the testing & its subsequent effect on the users of the subject software application being tested. Such information is helpful to the developers and the management in deciding the urgency or priority of fixing the bug during the product-testing phase.   Following Severity Levels are assigned during the Testing Phase: Critical – is the most dangerous level, which does not permit continuance of the testing effort beyond a particular point. Critical situation can arise due to popping up of some error message…

Ins and Outs of Software Quality Management According to ISO 8204, Quality is defined as: Totality of characteristics of an entity that bears on its ability to satisfy stated and implied needs. Introduction to sound Quality Management System: Software Quality Management involves set of pre-defined processes which are aimed to ensure that the Software Project would reach its goals. Or it can be said that the Software Project would meet the clients expectations. The Software Quality Management comprises of following three key elements 1) Quality Planning: Quality Planning is the most important step in Software Quality Management. In the Planning…

Introduction to CMM & CMMI Software Quality: It is the prime requirement of any Quality Software that it should reasonably be bug-free, delivered on time and within budgetary constraints. It should meet the defined requirements or expectations, and should be maintainable. Therefore to produce error free and high quality software there arises a great need that certain internationally recognized standards be followed. Quality Standards: Various Quality Standards are available ISO 9001: 2000 – is Quality Management System Certification. To achieve this, an organization is expected to satisfy the requirements defined in CL. 1 to 8 of ISO 9001: 2000 Six Sigma – is a process…

What are the CMM Levels for Companies Various Capability Maturity Levels � CMM Levels for Companies The Capability Maturity Model defines following levels for the organizations depending upon the processes being followed by them. CMM Level 0 – Companies: CMM � Level 0 companies are the ones, which do not have any structured Processes, Tracking Mechanisms & Plans. It is left to the developer or any person responsible for Quality to ensure that the product meets the expectations. CMM Level 1 – Companies: Work is Performed Informally CMM � Level 1 companies are the ones, where the teams put in extra hard work…

Classification Among Testing Before delving on various types of Testing, let us firstly understand the basic definitions of Software Testing Definition of Testing: Software Testing carries many definitions as explained by various practitioners. Definition  1: Testing is a process in which the defects are identified, isolated (separated), subjected (sending) for rectification and ensured that the product is defect free in order to produce a quality product in the end and hence customer satisfaction. Definition  2: Testing is the process of executing a software program with the intent of finding errors. Definition  3: Testing is the process of Verifying and validating the software application with respect…

Encyclopedia of Software Testing Terms Here is an Exhaustive Database of all Terms Exclusively Related to Software Testing Following Links direct you to the full length repository of definitions in an alphabetically sorted order A B C D E  F G H I J K L M N O PQ R S T U V W X Y Z Red Links have no data at the moment please. 1) This database explains various concepts, terms and definitions designed to help communication in the field of software testing and related disciplines. 2) Some of the definitions explained in the ISTQB document Glossary of Terms Ver. 2.0 Dec. 2007  have been listed 3) An effort has been made to make this…

White Box Testing – Introduction: White Box Testing Involves tests based upon coverage of code statements, branches, paths & conditions. For White Box testing, it is essential that the software tester should have in-depth knowledge of internal logic of an application’s code. Here the software tester uses his explicit knowledge of the internal workings of the item being tested to select the test data & uses his specific knowledge of programming code to examine the outputs. The white box test is accurate only if the tester knows what the program is supposed to do. He or she can then see…

Usability Testing or Usability Engineering Understanding Usability Engineering: Usability Engineering is an empirical science and has quite a simple definition. It studies the human interaction and cognitive behavior of an individual with respect to performing a task. It could be as simple as a driving a vehicle or using a product. Users interaction in performing a task should be in synchronization with the workflow of the product. Usability Engineering as a science helps in achieving this goal. Usability for a Product: A Product should be usable. It means that people can use a product easily and efficiently to accomplish their own…

Unit Testing: In software engineering, unit testing is a test (often automated) that validates that individual units of source code are working properly. A unit is the smallest testable part of an application. In procedural programming a unit may be an individual program, function, procedure, etc., while in object-oriented programming, the smallest unit is a method, which may belong to a base / super class, abstract class or derived / child class. Ideally, each test case is independent from the others; Double objects like stubs, mock or fake objects as well as test harnesses can be used to assist testing…

System Testing: System testing of software or hardware is testing conducted on a complete, integrated system to evaluate the system’s compliance with its specified requirements. System testing falls within the scope of black box testing, and as such, should require no knowledge of the inner design of the code or logic. As a rule, system testing takes, as its input, all of the “integrated” software components that have successfully passed integration testing and also the software system itself integrated with any applicable hardware system(s). The purpose of integration testing is to detect any inconsistencies between the software units that are…

Stress Testing: Stress testing is a form of testing that is used to determine the stability of a given system or entity. It involves testing beyond normal operational capacity, often to a breaking point, in order to observe the results. Stress testing may have a more specific meaning in certain industries. In software testing, stress testing often refers to tests that put a greater emphasis on robustness, availability, and error handling under a heavy load, rather than on what would be considered correct behavior under normal circumstances. In particular, the goals of such tests may be to ensure the software…

Smoke Testing: Smoke testing is a term used in plumbing, woodwind repair, electronics, and computer software development. It refers to the first test made after repairs or first assembly to provide some assurance that the system under test will not catastrophically fail. After a smoke test proves that the pipes will not leak, the keys seal properly, the circuit will not burn, or the software will not crash outright, the assembly is ready for more stressful testing. In software testing area, smoke testing is a preliminary to further testing, which should reveal simple failures severe enough to reject a prospective…

Security Testing: Security Testing is the process to determine that an IS (Information System) protects data and maintains functionality as intended. The six basic security concepts that need to be covered by security testing are as under. 1) Confidentiality: ($) A security measure which protects against the disclosure of information to parties other than the intended recipient that is by no means the only way of ensuring confidentiality. 2) Integrity: ($) A measure intended to allow the receiver to determine that the information which it receives has not been altered in transit or by other than the originator of the…

Sanity Testing: A sanity test or sanity check is a basic test to quickly evaluate the validity of a claim or calculation. In mathematics, for example, when dividing by three or nine, verifying that the sum of the digits of the result is a multiple of 3 or 9 (casting out nines) respectively is a sanity test. In computer science it is a very brief run-through of the functionality of a computer program, system, calculation, or other analysis, to assure that the system or methodology works as expected, often prior to a more exhaustive round of testing In software development,…

Regression Testing: Regression testing is any type of software testing which seeks to uncover regression bugs. Regression bugs occur whenever software functionality that previously worked as desired, stops working or no longer works in the same way that was previously planned. Typically regression bugs occur as an unintended consequence of program changes. After modifying software, either for a change in functionality or to fix defects, a regression test re-runs previously passing tests on the modified software to ensure that the modifications haven’t unintentionally caused a regression of previous functionality. These regression tests are often automated. More specific forms of regression…

Recovery Testing: Recovery testing is the activity of testing how well the software is able to recover from crashes, hardware failures and other similar problems. Recovery testing is the forced failure of the software in a variety of ways to verify that recovery is properly performed. Recovery testing should not be confused with Reliability testing, which is tries to discover the point at which failure occurs. Some the examples of recovery testing are: 1) While the application running, suddenly restart the computer and after that check the validness of application’s data integrity; 2) While application receives data from the network,…

Mutation Testing: Mutation testing (sometimes also called mutation analysis) is a method of software testing, which involves modifying program’s source code in small ways. These, so-called mutations, are based on well-defined mutation operators that either mimic typical user mistakes (such as using the wrong operator or variable name) or force the creation of valuable tests (such as driving each expression to zero). The purpose is to help the tester develop effective tests or locate weaknesses in the test data used for the program or in sections of the code that are seldom or never accessed during execution. Pioneered in the…

Load Testing: Load testing is the process of creating demand on a system or device and measuring its response. In software engineering it is a blanket term that is used in many different ways across the professional software testing community. Load testing generally refers to the practice of modeling the expected usage of a software program by simulating multiple users accessing the program’s services concurrently. As such, this testing is most relevant for multi-user systems, often one built using a client/server model, such as web servers. However, other types of software systems can be load-tested also. For example, a word…

Integration Testing: Integration testing (sometimes called Integration and Testing, abbreviated as I&T) is the phase of software testing in which individual software modules are combined and tested as a group. It follows unit testing and precedes system testing. Integration testing takes as its input modules that have been unit tested, groups them in larger aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as its output the integrated system ready for system testing. Purpose of Integration Testing: The purpose of integration testing is to verify functional, performance and reliability requirements placed on major design items.…

Glass Box Testing: Glass Box Testing is an exact contrast of Black Box testing & is structural testing, where test data are derived from direct examination of the code to be tested. Glass-box test design allows one to peek inside the “box”, and it focuses specifically on using internal knowledge of the software to guide the selection of test data. This type of structural testing is sometimes referred to as clear-box testing since white boxes are considered opaque and do not really permit visibility into the code. For glass box testing, the test cases cannot be determined until the code…

Exploratory Testing: Exploratory testing is the tactical pursuit of software faults and defects driven by challenging assumptions. It is an approach in software testing with simultaneous learning, test design and test execution. While the software is being tested, the tester learns things that together with experience and creativity generates new good tests to run. Exploratory testing has similarities to ad hoc testing. Description: Exploratory testing seeks to find out how the software actually works, and to ask questions about how it will handle difficult and easy cases. The testing is dependent on the tester’s skill of inventing test cases and…

End To End Testing What is End To End (E2E) Testing? Many subsystems are tested in isolation. This is fine for many scenarios that are local to that subsystem, but there are some scenarios that cross the boundary of several subsystems. This is good because a lot of testing can be done in isolation but at some point a complete end to end test needs to be carried out on the whole system. Problems and Issues: Unfortunately a lot of testing of complex systems is carried out manually because the level of effort to automate the E2E test is considered…

Dynamic Testing: Dynamic testing (or dynamic analysis) is a term used in software engineering to describe the testing of the dynamic behavior of code. That is, dynamic analysis refers to the examination of the physical response from the system to variables that are not constant and change with time. In dynamic testing the software must actually be compiled and run; this is in contrast to static testing. Dynamic testing is the validation portion of Verification and Validation. Some of dynamic testing methodologies include unit testing, integration testing, system testing and acceptance testing. Dynamic Testing involves working with the software, giving…

Compatibility Testing: Compatibility testing is used to determine if your software application has issues related to how it functions in concert with the operating system and different types of system hardware and software. What is the purpose of Compatibility Testing? Your internal QA department has done all it can to ensure that your software functions as designed. The light is shining at the end of the development tunnel; your product is nearing completion, and the release deadline is rapidly approaching. You know that the application functions on all of your in-house computers. What about the myriad of computer systems of…

Client Server Testing : Client-Server Testing Technology Client Server Software : Client-server software requires specific forms of testing to prevent or predict catastrophic errors. Servers go down, records lock, I/O (Input/Output) errors and lost messages can really cut into the benefits of adopting this network technology. Testing addresses system performance and scalability by understanding how systems respond to increased workloads and what causes them to fail. Software testing is more than just review. It involves the dynamic analysis of the software being tested. It instructs the software to perform tasks and functions in a virtual environment. This examines compatibility, capability, efficiency,…

Black Box Testing – Introduction : Black-Box Testing Involves tests based upon specifications requirements and functionality. For Black Box testing, the software tester need not have any knowledge of internal design of the software or its code being tested. Due to this reason, the tester and the programmer can be independent of each other, avoiding programmer bias toward his own work. During black box testing, the tester would only know the “legal” inputs and what the expected outputs should be, but he need not know as to how the program actually arrives at those outputs. Due to the nature of black box testing,…

Ad-hoc Testing: Ad hoc testing is a commonly used term for software testing performed without planning and documentation. The tests are intended to be run only once, unless a defect is discovered. Ad hoc testing is a part of exploratory testing, being the least formal of test methods. In this view, ad hoc testing has been criticized because it isn’t structured, but this can also be a strength: important things can be found quickly. It is performed with improvisation, the tester seeks to find bugs with any means that seem appropriate. It contrasts to regression testing that looks for a…

Acceptance Testing Acceptance testing is the customer or the end user evaluation of the system, primarily to determine whether the system meets their needs and expectations. Generally the customer does the Acceptance Testing with the assistance from developers. Customers can evaluate the system either by conducting a benchmark test or by a pilot test. The benchmark test involves evaluation of system performance against the test cases, which represent typical conditions under which the system will operate when actually installed. The pilot test involves installation of the system on an experimental basis, and the system is then evaluated against everyday working.…

Glossary of Terms beginning Alphabet-w Walkthrough: Walkthrough is A step-by-step presentation by the author of a document in order to gather information and to establish a common understanding of its content. It is an informal meeting for evaluation or informational purposes. Little or no preparation is usually required. During a walkthrough, the producer of a product “walks through” or paraphrases the products content, while a team of other individuals follow along. The objective of the team remains to raise questions and raise issues about the product which may lead to the identification of defects. Weak Mutation Coverage: Weak Mutation Coverage is…

Glossary of Terms beginning Alphabet-V Validation: Validation refers to the determination of the correctness of the final program or software product produced from a development project with respect to the user needs and requirements. The techniques for validation are testing, inspection and reviewing. Validation typically involves actual testing and takes place after verifications are completed. As per the definition of ISO-9000, Validation is confirmation by examination and through provision of objective evidence that the requirements for a specific intended use or application have been fulfilled. Validation Protocol: Validation Protocol is a written plan stating how validation will be conducted, including…

Glossary of Terms beginning Alphabet-U Understandability: Understandability is the capability of the software product to enable the user to understand whether the software is suitable, and how it can be used for particular tasks and conditions of use. Unit Testing: Unit Testing involves testing of individual programs, modules, or components to demonstrate that the program executes as per the specifications and it validates the design and technical quality of the application. The focus is on ensuring that the detailed logic within the component is accurate and reliable according to the pre-defined specifications. In Unit Testing, the Called Components (or Communicating Components) are…

Glossary of Terms beginning Alphabet-T Table Coverage: Table coverage is a metric, which indicates whether each entry in a particular array has been referenced. This is useful for programs, which are controlled by a finite state machine.  Technical Review: Technical Review refers to a peer group discussion activity that focuses on achieving consensus on the technical approach to be taken. A technical review is also known as a peer review. Test: Test is an activity in which a system or component is executed under specified conditions, the results are observed or recorded and an evaluation is made of some aspect of the…

Glossary of Terms beginning Alphabet-S Safety: Safety is the capability of the software product to achieve acceptable levels of risk of harm to people, business, software, property or the environment in a specified context of use.   Safety Testing: Safety Testing is the process of testing to determine the safety of a software product. Safety Test Analysis: Safety Test Analysis is an analysis demonstrating that safety requirements have been correctly implemented and that the software functions safely within its specified environment. Tests may include; unit level tests, interface tests, software configuration item testing, system level testing, stress testing, and regression testing.   Sanity…

Glossary of Terms beginning Alphabet-R Race Condition / Coverage: Race Condition is a cause of concurrency problems. It refers to multiple accesses to a shared resource, at least one of which is a write, with no mechanism used by either to moderate simultaneous access. It helps detect failure to synchronize access to resources. It is useful for testing multi-threaded programs such as in an operating system. Ramp Testing: Ramp Testing involves continuously raising an input signal until the system breaks down. Random Testing: Random Testing is a black box test design technique where test cases are selected, possibly using a pseudo-random…

Glossary of Terms beginning Alphabet-Q Qualification Testing: Qualification Testing is a formal testing, usually conducted by the developer for the consumer, to demonstrate that the software meets its specified requirements. Quality: Quality is the degree to which a component, system or process meets specified requirements and/or user/customer needs and expectations. A product is considered a quality product if it is free from defects. From the perspective of a producer, a product is a quality product if it meets or conforms to the statement of requirements which defines the product. From perspective of the customer, quality means “fitness for use.” Quality…

Glossary of Terms beginning Alphabet-P Pair Programming: Pair Programming is a software development approach whereby lines of code (production and/or test) of a component are written by two programmers sitting at a single computer. This implicitly means ongoing real-time code reviews are performed. Pair Testing: Pair testing means when two testers work together to find defects. Typically, they share one computer and trade control of it while testing. Parallel Testing: Parallel Testing involves testing a new or an altered data processing system with the same source data that is used in another system. The other system is considered as the standard…

Glossary of Terms beginning Alphabet-O Object Code Branch Coverage: Object code branch coverage is a metric, which reports whether each machine language conditional branch instruction both took the branch and fell through. It gives results which depend on the compiler rather than on the program structure since compiler code generation and optimization techniques can create object code that bears little similarity to the original source code structure.  Off-the-Shelf Software: Off-the-Shelf Software is a software product that is developed for the general market, i.e. for a large number of customers, and that is delivered to many customers in identical format. Operability: Operability is…

Glossary of Terms beginning Alphabet-N N-switch Coverage: N-switch Coverage is the percentage of sequences of N+1 transitions which have been exercised by a test suite. N-switch testing: N-switch testing is a form of state transition testing in which test cases are designed to execute all valid sequences of N+1 transitions. Negative Testing: Negative Testing is aimed at showing that the software does not work. Negative Testing refers to the testing the application for failure like conditions. It involves testing the tool with improper inputs. for example entering the special characters in place of a phone number N+1 Testing:  N+1 Testing is a…

Glossary of Terms beginning Alphabet-M Maintenance: Maintenance is the modification of a software product after delivery to correct defects, to improve performance or other attributes, or to adapt the product to a modified environment. Maintenance Testing: Maintenance Testing refers to the testing of changes to an operational system or the impact of a changed environment to an operational system. Maintainability: Maintainability is a quality attribute pointing towards an effort required in locating and fixing an error in an operational program.   Maintainability Testing: Maintainability Testing is the process of testing to determine the maintainability of a software product. Management Review:…

Glossary of Terms beginning Alphabet-L LCSAJ: LCSAJ means “Linear Code Sequence And Jump”, consists of the following three items (conventionally identified by line numbers in a source code listing like 1) The start of the linear sequence of executable statements 2) The end of the linear sequence, and 3) The target line to which control flow is transferred at the end of the linear sequence. LCSAJ Coverage: LCSAJ Coverage is the percentage of LCSAJ�s of a component which have been exercised by a test suite. 100% LCSAJ coverage implies 100% decision coverage. LCSAJ Testing: LCSAJ testing is a white box test…

Glossary of Terms beginning Alphabet-K Keyword Driven Testing: Keyword Driven Testing is a scripting technique which uses data files to contain not only test data and expected results, but also the keywords related to the application being tested. The keywords are interpreted by special supporting scripts which are called by the control script for the test. Explanation to All Alphabets in the Glossary of Terms

Glossary of Terms beginning Alphabet-G Glass Box Testing: Glass Box Testing is an exact contrast of Black Box testing & is structural testing, where test data are derived from direct examination of the code to be tested. Glass-box test design allows one to peek inside the “box”, and it focuses specifically on using internal knowledge of the software to guide the selection of test data. Gorilla Testing: Gorilla Testing involves testing one particular module, functionality heavily. Gray Box Testing: Gray Box Testing is a combination of Black Box and White Box testing methodologies: testing a piece of software against its…

Glossary of Terms beginning Alphabet-F Fail: A test is considered as fail if its actual result does not match its expected result. Failure: Failure means actual deviation of the component or system from its expected delivery, service or result. Failure Mode: Failure Mode refers to the physical or functional manifestation of a failure. For example, a system in failure mode may be characterized by slow operation, incorrect outputs, or complete termination of execution. Failure Mode and Effect Analysis (FMEA): Failure Mode and Effect Analysis is a systematic approach to risk identification and analysis of identifying possible modes of failure and attempting to…

Glossary of Terms beginning Alphabet-E Efficiency: Efficiency is a quality attribute pointing towards the amount of computing resources and code required by the program to perform a particular function. It is the capability of the software product to provide appropriate performance, relative to the amount of resources used under stated conditions. Efficiency Testing: Efficiency Testing is the process of testing to determine the efficiency of a software product. Elementary Comparison Testing: Elementary Comparison Testing is a black box test design techniques in which test cases are designed to execute combinations of inputs using the concept of condition determination coverage. Emulator: Emulator is…

Glossary of Terms beginning Alphabet-D Data Definition: Data Definition is an executable statement where a variable is assigned a value. Data Dictionary: Data Dictionary is a database that contains definitions of all data items defined during analysis. Data Driven Testing: Data Driven Testing is a testing in which the action of a test case is parameterized by externally defined data values, maintained as a file or spreadsheet. It is a common technique in Automated Testing. Data Flow: Data Flow is an abstract representation of the sequence and possible changes of the state of data objects, where the state of an object…

Glossary of Terms beginning Alphabet-C CASE:  CASE refers to Computer Aided Software Engineering. CAST:  CAST refers to Computer Aided Software Testing. Call Coverage: Call coverage is a metric, which reports whether you executed each function call. The hypothesis is that bugs commonly occur in interfaces between modules. It is also known as call pair coverage. Capture / Replay Tool: Capture / Replay Tool is a test tool which 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 it is…

Glossary of Terms beginning Alphabet-B Back-To-Back Testing: Back-To-Back Testing refers to the testing process in which two or more variants of a component or system are executed with the same inputs, the outputs compared, and analyzed in cases of discrepancies. Backus-Naur Form: Backus-Naur Form is a meta-language used to formally describe the syntax of a language. Basic Block: Basic Block is a sequence of one or more consecutive, executable statements containing no branches. Basis Path Testing: Basis Path Testing is a white box test case design technique that uses the algorithmic flow of the program to design tests. Basis Set:…

Glossary of Terms beginning Alphabet-A Acceptance Criteria: Acceptance Criteria is the exit criteria which a component or system is expected to satisfy in order to be accepted by the end user, customer or any other authorized agency. Acceptance Testing: Acceptance Testing is the best industry practice & its is the final testing conducted to enable a user / customer to determine whether to accept a software product. It is normally performed to validate the software meets a set of agreed acceptance criteria based on specifications provided by the end-user or customer. In theory when all the acceptance tests pass, it…

Professor Noriaki Kano : Professor Noriaki Kano had been the developer of a program whose simple ranking scheme distinguishes between essential and differentiating attributes related to concepts of customer quality. This system is referred to as the Kano Model. Noriaki Kano was the 1997 recipient of the Deming Prize for Individuals. References: Wikipedia � Free Encyclopedia Many More Articles on Quality Perspectives

Prof. Joseph Moses Juran : Prof. Juran was a 20th Century management consultant who is remembered as an evangelist for quality and quality management, writing several influential books on those subjects. Prof. Juran was a 20th Century management consultant who is remembered as an evangelist for quality and quality management, writing several influential books on those subjects. Juran was born to a Jewish family in 1904 in, Romania, and in 1912, he immigrated to America. In 1941 Juran expanded the Pareto principle applying it to quality issues (e.g. 80% of a problem is caused by 20% of the causes). This…

Dr. Genichi Taguchi : Dr. Genichi Taguchi was an engineer and statistician born in 1924 in Tokamachi town of Japan. In 1950, he joined the Electrical Communications Laboratory of the Nippon Telegraph and Telephone Corporation just as statistical quality control was beginning to become popular in Japan under the influence of W. Edwards Deming and the Japanese Union of Scientists and Engineers. Taguchi spent his twelve years in developing methods for enhancing quality and reliability. Even at this point, he was beginning to be consulted widely in Japanese industry, with Toyota being an early adopter of his ideas.  References: Wikipedia…

Dr. W Edwards Deming: Dr. Deming continues to be widely revered in Japan for awakening the Japanese to the need for, and the possibilities in, a focus on quality. That included defining a quality product, and then reducing process variability to the point at which that product could be delivered to the customer in a timely and economical manner. Famous 14 points advocated by Deming on Quality 1) Create constancy of purpose. 2) Adopt the new philosophy. 3) Cease dependence on mass inspection to achieve quality. 4) Minimize total cost, not initial price of supplies. 5) Improve constantly the system of…

Types of Software Testing-At a Glance Software Testing Classification The development process involves various types of testing. Each test type addresses a specific testing requirement. The most fundamental types of testing involved in the development process are: Unit Testing System Testing Integration Testing Functional Testing Performance Testing Beta Testing Acceptance Testing The industry experts based upon the requirement have categorized many types of Software Testing. Following list presents a brief introduction to such types.   Acceptance Testing : Is the best industry practice & its is the final testing based on specifications provided by the end-user or customer, or based…

Progressive Definition of Quality: It is defined entirely by the customer or the end user and is based upon the evaluation of his entire experience as a customer. The customer experience is the aggregate of all the touch points that customers have with the company’s product and services. For example, when someone buys a product he forms an impression based on how it was sold, how it was delivered, how it performed, how well it was supported etc. By ISO 9000:Degree to which a set of inherent characteristic fulfills requirements By Dr. W Edwards Deming: The totality of features and characteristics of…

Structure of Software Testing Process 1) Team of Feature Owners: It is a top-level team in the hierarchy, which directly interacts with the prospective customers. It is responsible to minutely understand the customer requirements and groups them into several features. Various members in such a team may become the owners of some of such features. The team members take due initiative and actively interact with various teams become instrumental in providing necessary directions in developing the features owned by them. 2) User Interface Team: The User Interface called UI in short is extremely significant for the product. Even The UI team designs UI…

Introduction to Software Testing Software testing is the process used to assess the quality of computer software. Quality is not limited to, the process of executing a program or application with the intent of finding software bugs. Software Faults: The software faults occur through the following process. Whenever a software developer commits some mistake, which results in a defect (fault, bug) in the software source code. If this defect is executed, in certain situations the system will produce wrong results, causing a failure. Not all defects will necessarily result in failures. A defect can turn into a failure when the environment is…

Tutorial-2 How to design a Scenario for Load testing using HP-LoadRunner A suggestion of great value: Before practicing these Tutorials on “LoadRunner � from HP”, it is recommended that you acquire a preliminary working knowledge of using this wonderful tool. This can be easily attained by careful study of the “Frequently Asked Questions � FAQ�s” brought to you by this web site for the first time by Clicking on the following link: Learn the Basics of HP LoadRunner through FAQ’s <<<<<<<< =========== >>>>>>>> Brief Introduction of Scenario: A scenario is a file containing all the information about groups of Vusers which emulate human users during…

Quality Center Certification Skill Test: Q. 371 to 380 Objective Type / Multiple Choice Questions on HP Quality Center 9.2 under the Series (Quickly Review Your HP – QC Skills before appearing for HP Certification Exam HP0-M15) Set of 10 Questions Correct Answers to Earlier Questions – Q. 361 to Q 370 are at the end of this page: Q. 371: What does the Direct Cover Status of a requirement indicate? A. The type of parent requirement B. The execution status of linked tests C. The component of the application covered D. Whether the requirement has any linked defects  …