MODEL TEST PAPER I FIRST TERM EXAMINATION SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] ‘Time. 1.30 Hours M.M.:30 Note: Q.No.1 is compulsory. Attempt any two from the rest. =~ Q.1. (a) Difference between testing and debugging. (3) Testing Debugging 1, Testing always starts with known 1. Debugging starts from possibly un- conditions, uses predefined methods, known initial conditions and it’s end and has predictable outcomes too. cannot be predicted, apart from statis- tically. 2. Testing can and should definitely 2. The procedures for, and period of, be planned, designed, and scheduled. debugging cannot be so constrained. It proves a programmers failure. 3. It is the programmer's vindication. It is a demonstration of error or 4. It is always treated as a deductive apparent correctriess. process. : 5. Testing as executed should strive 5. Bebugging demands intuitive leaps, to be predictable, dull, constrained, conjectures, experimentation, and some rigid, and inhuman. freedom also. 6, Much of the testing can be done 6. Debugging is impossible without detailed without design knowledge. design knowledge. 7. Itean often be done by an outsider. | 7. Itmust be done by an insider. & Much of test-execution and design | 8 Automated debugging is still a dream for can be automated. programmers. 9. Testing purpose is to find bug. 9. Debugging purpose is to find cause of bug. Q.1. (b) Explain the role of process in software quality. (6) ‘Ans. Software quality management is a management process the goal of which is to develop and manage the quality of software to make sure the product satisfies the user. The goals of SQM (software quality management ) is to make sure a product isin good levels of quality and meets the regulations and standards the customer needs from the product. Software quality managers have to test the product before it's released to the market, they do this by a series of steps called the software cycle in order to got the errors in a software and try to fix it before being released. Their job is not only to make sure the software is in good shape for the consumer, but also to encourage the ‘quality culture to everyone and avoid fraud by protecting their software through proper development. Q.1. (c) Discuss the term “No silver bullets”. 2) ‘Ans. ‘No silver bullets” means “there is no single development, in either technology or management technique, which by itself promises even one order of magnitude [tenfold] improvement within a decade in productivity, in reliability, in simplicity.” He also2-MTP-I _ Seventh Semester, Software Testing and Quality Assurance states that “we cannot expect ever to see two-fold gains 1. as there is in hardware development. ioe Bape pug, fault, failure, test case, test Q.2. Explain the difference between error, sos suite. 2 Error: A discrepancy between a computed, observed, or measured value or condition and the true, specified, or theoretically correct value or condition. This can be a misunderstanding of the internal state of the software, an oversight in terms of memory mnanagement, confusion about the proper way to calculate a value, ete. Failure: The inability of a system or component to perform its required functions within epecified performance requirements. See: bug, crash, exception, and fault. Bug: A fault in a program which causes the program to perform in an unintended or unanticipated manner. See: anomaly, defect, error, exception, and fault. Bug is terminology of ‘Tester. * Fault: An incorrect step, causes the program to perform in an uninte defect, error, exception. . A test suite, less commonly known as a ‘validation suite’, is a collection of test cases that are intended to be used to test a software program, to show that it has some specified set of behaviours. A test suite often contains detailed instructions or goals for cach collection of test cases and information on the system configuration to be used during testing. A group of test cases may also contain prerequisite states or steps, and descriptions of the following tests. Collections of test cases are sometimes incorrectly termed a test plan, a test script, or even a test scenario. - Example test case template is as shown every two years” in software process, or data definition in a computer program which nded or unanticipated manner. See: bug, ID 14 Title ‘Add customer Pre-Conditions _._ Sign in with sales authorization ‘Test Steps 1. Select the client module. 2, Enter the customer information. 8, Click "Ada". Expected Results A message appears in the program's status bar. The message reads "New" customer added” Q.3. Explain code complexity testing and data flow testing. 10) ‘Ans. Complexity is a software metric (measurem ioindice ¢ ftw: ent), used to indi i ofa program, It is a quantitative measure of the number ‘oftinewy sade pendent paths through a program's source code. i dnslependent Bee Cyclomatic complexity is computed usin, ig the contro! nodes of the graph correspond to indivisible groups tomes directed edge connects two nodes if the second command might after the first command, Cyclomatic complexity may ale functions, modules, methods or classes within a progr, “ One testing strategy, called basis path testiny ( to test cach linearly independent path throu test cases will equal the cyclomatic comple: ‘@raph of the program: the ands of a program, and & tbe executed immediately be applied to individual 1g by McCabe who first iti : Cab proposed it, is gh the program; in this case, the number of xity of the program.LP. University-(B.Tech)-Akash Books MTP-I-3 ‘The cyclomatic complexity of a section of sourcecode is the number of linearly independent paths within it, For instance, if the source code contained no control flow statements (conditionals or decision points), the comploxity would be 1, since there would be only a single path through the code. If the code had one single-condition IF statement, there would be two paths through the code: one where the IF statement evaluates to TRUE and another one whore it evaluates to FALSE, so the complexity would be 2. Two nested single-condition IFs, or one IF with two conditions, would produce ~ a complexity of 4. Mathematically, the cyclomatic complexity of a structured program[a] is defined with reference to the control flow graph of the program, a directed graph containing the basic blocks of the program, with an edge between two basic blocks if control may pass from the first to the second. The complexity M is then defined as{2] M=E-N+2P, where B= The number of edges of the graph. . N= The number of nodes of the graph. P= The number of connected components. Data flow testing is a family of test strategies based on selecting paths through the program’s control flow in order to explore sequences of events related to the status of variables or data objects. Dataflow Testing focuses on.the points at which variables receive values and the points at which these values are used. Data Flow testing helps us to pinpoint any of the following issues: * Avariable that is declared but never used within the program. + Avariable that is used but never declared. * Avatiable that is defined multiple times before it is used. * De-allocating a variable before it is used. Q.4. (a) Difference between verification and validation. (5) Verification Validation L._ Verification is a static practice of 1, Validation is a dynamic mechanism of verifying documents, design, code validating and testing the actual product. and program. 2. It does not involve executing the 2, It always involves executing the code. code. 3. Itis human based checking of ‘3. Itis computer based execution of program. documents and files. 4. Verification uses_methods like 4, Validation uses methods like black box inspections, reviews, walkthroughs, (functional) testing, gray box testing, and and Desk-checking.ete. white box (structural) testing ete. .5, Verification is to check whether 5, Validation is to check whether software the software conforms to-specifica- meets the customer expectations and tions, requirements. 6. Ibean catch errors that validation 6, Itean catch errors that verification cannot cannot catch. It is low level exercise. |. catch, It is High Level Exercise. ‘1. ‘Target is requirements specification °} 7. Target is actual product-a unit, a module, application and softwate architec a bent of integrated modules, and ture, high level, complete design, offective final product. and database design ete.L-MTPI Seventh Semester, Software Testing and Quality Assurance ®. Verification is done by QA team @, Validation is carried out with the to ensure. that the software is as involvement of testing team. per the specifications in the SRS document. oo 9. Tt generally comes first-done before | 9. It generally follows after verification. validation, Q.4. (6) Discuss limitations of testing. 3) Testing Limitations * You cannot test a program completely * We can only test against system requirements *May not detect errors in the requirements. + Incomplete or ambiguous requirements may lead to inadequate or incorrect testing. * Exhaustive (total) testing is impossible in present scenario. * Time and budget constraints normally require very careful planning of the testing effort. + Compromise between thoroughness and budget. * Test results are used to make business decisions for release dates. « Even if you do find the last bug, you'll never know it © You will run out of time before you run out of test cases “e You cannot test every path * You cannot test every valid input * You cannot test every invalid inputMODEL TEST PAPER I SECOND TERM EXAMINATION SEVENTH SEMESTER [B.TECH] : SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] ‘Time. 1.80 Hours: MM. :30 Note: Q. no. 1 is compulsory and attempt any tivo from the rest. Qu. (a) Explain TQM. (6) Ans, Total quality management (TQM) consists of organization-wide efforts to install and make pormanont.a climate in which an organization continuously improves its ability to deliver high-quality products and servicos to customers, While there is no widely agreed-upon approach, TQM offorts typically draw heavily on the previously developed tools and techniques of quality control strike out. The key concepts in the TQM + “Top management has direct responsibility for quality improvement.” + “Increased quality comes from systematic analysis and improvement of work processes.” improvement is a continuous offort and conducted throughout the The Navy used the following tools and techniques: « The PDCA cycle to drive issues to resolution * Ad hoe cross-functional teams (similar to quality circles) responsible for addressing immediate process issues * Standing cross-functional teams responsible for the improvement of processes over the long term « Active management participation through steering committees + Use of the Seven Basic Tools of Quality to analyze quality-rolated issues. Q.1. (b) Explain the difference betweon CMM and CMMI. © ‘Ans. CMM: CMM is not intended to cover all the aspects of software development and systems development, It provides a sot of guidelinos for managing software developments and for making changes over time. Tho guidelines center on best practices, software engineering inputs, extrapolation from other areas and real-world experience. The guidelines are supposed to serve as a framo of reforonce rather than a rigid list to follow, with each organization shaping them to its own needs. CMMI: Some CMMs have come about for different areas, and CMMI has incorporated some of these different CMMs, For instance, CMMI has integrated the CMM for software (SW-CMM) and the integrated produet development (IPD) CMM. CMMI identifies 25 process areas in the development process, Each process area defines a set of specific goals, as woll ns specific practices to achiovo tho goals. ___ CMM and CMMI Differences: CMM camo about to tackle processes in different industries separately, but CMMI integrates tho processes for difforent industrias. CMMI combines the best features of cach model, CMMI has retainod the maturity levels used ocean annero Testing and Quality Assurance ter, Softwar . th Semes! Jes of the maturity levels and addeq Rey “G-MTP-I Seven! . somo changes ta the tit by CMM but has made a processes. more toward large, bureauera , re geare' ai CMMI and CMM point out they are cenization s have to spend riore time se oxganizations than smaller nes, Sm ET individual contexts. Anothe interpreting the provisions of CI and cM ocus on the process while not dvellng gy criticism holds that CMM and CMM argo ene meaning that implementing the people and technology aspects of soRwwant Tet them provides no guarantee that a projec a ‘tj ing and management. Q2. Explain test planning a san you wil boablo Fdooatiact, ‘Test planning: By writing a compelling tet vod Ser system meets requirement strategy approach to be used to verify that your product oF ment and design specifications. * It will specify what type of meet success criteria. + It will define the testing tasks and cycles + It will define and document how to manage testing and the parameters by which it will be controlled » Building test plans that are rigorous and tailored to meet the specific needs of your testing program’s, budget and timescales. . + Identify, profile and manage risk ; * Identify and build the right test cases that exercise and prove if the system meets specified phase level and overall acceptancé criteria * Build the information traceability you require to manage testing progress through each software testing life cycle stage; : 5 * Work within traditional, v-model, Agile, or other preferred software testing life cycles ‘Test management most commonly refers to the activity of managing the computer software testing process. A test management tool is software used to manage tests(automated or manual) that have been previously specified by a test procedure. It is often associated with automation software. ‘Test management tools often include requirement and/or specification management modules that e " allow automatic generation of the requirement test matrix (RTM), which is one of the main metrics t indicate functional coverage of a system under test (SUT). This includes building some bundles of test “ 7 sine Been ane cn ees or met am (rele Maniual execution: The user will have to z inform the system of the result. Sorie test eee all the test steps manually, ant {interface the user with the test plan to facilitate this tent oe nse 8 ramework tests. The simplest way torun a testis toruna test exc pyar are Several Way tome tease. The test case can be associate with other test artifacts such as test plan t 8, i Be execution records, and test suites.” “°S* Serpts, test environments, test 8° testing and when and how often you should test ipMTP-I-7 Q.3, Explain Six sigma concepts. qo) ‘Ans, Six Sigma is a management philosophy developed by Motorola that emphasizes setting extremely high objectives, collecting data, and analyzing results to crime degree as a way to reduce dofect8 in products and services. The Greek letter sigria aime cotimes used to denote variation from a standard. The philosophy behind Six Signa is that ityou measure how many defects are in a process, you can figure out how iauystematically eliminate them and get as close to perfection as possible. In order for i Smpany to achieve Six Sigma, it cannot produce more than 8.4 defects per million opportunities, where an opportunity is defined as a chanee for non- conformance, ‘There are two Six Sigma processes: Six Sigma DMAIC and Six Sigma DMADV, each term derived from the major steps in the process. Six Sigma DMAIC is a process that defines, measures, analyzes, improves, and controls existing processes that fall below the Six Sigma specification, Six Sigma DMADV defines, measures, analyzes, designs, and verifies new processes or products that are trying to achieve Six Sigma Quality Ail Six Sigma processes are executed by Six Sigma Green Belts or Six Sigma Figck Belts, which are then overseen by a Six Sigma Master Black Belts, terms created by Motorola. Six Sigma proponents cl reduction, eycle-time improveme! customer requirements, increase and services. It is acknowledged that Six take several years before a company begins t tat amonts, Seientifie-Atlanta, General Electric, and Allied Signal are a few of the companies that practice Six Sigma. Q.4. Discuss various types of acceptance testing. qo) ‘Ans. Acceptance testing, a testing technique performed to determine whether oF not the software system has met the requirement specifications. The main purpose of this test is to evaluate the system’s compliance with the business requirements and verify if it is has met the required criteria for delivery to end users. ‘There are various forms of acceptance testing: + Business acceptance Testing « User acceptance Testing + Beta Testing + Alpha Testing _ In SDLC: The following diagram explains the fitment of - Acceptance Testing acceptance testing in the software development life cycle. LP. University-(B.Tech)-Akash Books Jaim that its benefits include up to 50% process cost nt, less waste of materials, a better understanding of ‘d customer satisfaction, and more reliable products Sigma can be costly to implement and can ‘0 see bottom-line results. Texas Integration testing: i ality Assurance G-MTPI Seventh Semester, Software Testing and Qu xs . against the test data or using an acceptance ith the expected ones. ei defined on the basis ofthe following The acceptance test cases are executed test script and then the results are compare Acceptance Criteria: Acceptance criteria are attributes * Functional Correctness and Completeness * Data Integrity + Data Conversion * Usability + Performance + Timeliness * Confidentiality and Availability * Installability and Upgradability * Scalability * Documentation Acceptance Test Plan - Attributes: The acceptance test activities are carried out in phases. Firstly, the basic tests are executed, and if the test results are satisfactory then the execution of more complex scenarios are carried out. ‘The Acceptance test plan has the following attributes: * Introduction * Acceptance Test Category * Operation Environment * Test case ID * Test Title * Test Objective * Test Procedure * Test Schedule * Resources The acceptance test activities are designed to reach at one of the conclusions: 1. Accept the system as delivered 2. Accept the system after the requested modificati 3. Do not accept the system . matiSeatons have Heén made Acceptance Test Report - Attributes The Acceptance test Report has the followin, * Report Identifier * Variations + Recommendations * Summary of To-DO List * Approval Decision iE attribute;MODEL TEST PAPER I END TERM EXAMINATION SEVENTH SEMESTER [B.TECH] . SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] Time. 3 Hours MM. : 75 Note: Question no. 1 is compulsory and attempt any 4 questions from the rest. Q.1. (a) Define system testing. (2) ‘Ans. 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 o logic. Q.1. (6) Draw a structure showing various testing techniques. (3) Testing techniques wee Slatic testing Dynamic testing a White box testing] | Block box testing Informal review Equivalence partivoning| Equivalence partitioning} "Technical review [Bouncary valve analysis| [Boundary value analysis| ‘Al-Pairs testing Al-Pairs testing Walkthrough Inspection State transition tables State transition tables Decision table testing Decision table testing Use case testing Use case testing Q.1. (e) Define defects. (3) Ans. Adefect is an error or a bug, in the application which is created. A programmer while designing and building the software can make mistakes or error. These mistakes or errors mean that there are flaws in the software. These are called defects. * When actual result deviates from the expected result while testing a software application or product then it results into a defect. Hence, any deviation from the specification mentioned in the produet functional specification document is a defect. In different organizations it’s called differently like bug, issue, incidents or problem. * When.the result of the software application or product does not meet with the end user expectations or the software requirements then it results into a Bug or Defect.10-MTP-I. Seventh Semester, Software Testing and Quality Assurance ‘These defects or bugs occur because of an error in logic or in coding which results ini failure or unpredicted or unanticipated results. Q.1. (dyExplain V model for software testing. és ‘Y- model means Verification and Validation model. Just like the waterfall mogg, the V-Shaped life cycle is a sequential path of execution of processes. Each phase mus, be completed before the next phase begins. Testing of the product is planned in paraljg, with a corresponding phase of development. ‘The various phases of the V-model are as follows: Requirements like BRS and SRS begin the life cycle model just like the waterfall model. But, in this model before development i started, a system test plan is created, The test plan focuses on meeting the functionality specified in the requirements gathering. op, F Testers life cycle Developer's life cycle] (Verification phase) (Werification phase) | x Acceptance testing BRS (Business req. specifications) X\ = SRS (System req. specifications) HLD (High level ‘System design) integration testing \ LD fae eve | ——+feonponat etn] Coane} tress ] The high-level design (HLD) phase focuses on system architecture and design. It provide overview of solution, platform, system, product and service/process. An integration test plan is created in this phase as well in order to test the pieces of the software systems ability to work together. The Iow-leyel design (LLD) phase is where the actual software components are designed. It defines the actual logic for each and every component of the system. Class diagram with all the methods and relation between classes comes under LLD. Component tests are created in this phase as well.I } f | LP. University-(B.Tech)-Akash Books MTP-I-11 ‘The implementation phase is, again, where all coding takes place. Once coding is complete, the path of execution continues up the right side of the V where the test plans developed earlier are now put to use. Coding: This is at the bottom of the V-Shape model. Module design is converted into code by developers. Advantages of V-model: * Simple and easy to use. + Testing activities like planning, test designing happens well before coding. This saves a lot of time. Hence higher chance of success over the waterfall model. * Proactive defect tracking — that is defects are found at early stage. * Avoids the downward flow of the defects. + Works well for small projects where requirements are easily understood. Disadvantages of V-model: * Very rigid and least flexible. * Sofiware is developed during the implementation phase, so no early prototypes of the software are produced. ° * Ifany changes happen in midway, then the test documents along with requirement documents has to be updated, Q.1. (e) Explain regression testing tools. @) Ans. Regression means retesting the unchanged parts of the application. Test cases are re-executed in order to check whether previous functionality of application is working fine and new changes have not introduced any new bugs. This test can be performed on a new build when there is significant change in original functionality or even a single bug fix. ‘This is the method of verification. Verifying that the bugs are fixed and the newly added features have not created in problem in previous working version of software. Testers perform functional testing when new build is available for verification. The intend of this test is to verify the changes made in the existing functionality and newly added functionality. When this test is done tester should verify if the existing functionality is working as expected and new changes have not introduced any defect in functionality that was working before this change. Regression test should be the part of release cycle and must be considered in test estimation. Regression testing is usually performed ‘after verification of changes or new functionality. But this is not the case always. For the release taking months to complete, regression tests must be incorporated in the daily test cycle. For weekly releases regression tests can be performed when functional testing is over for the changes. Regression Testing Tools: Automated Regression Testing is the testing area where we can automate most of the testing efforts. We run all the previously executed test cases on new build. This means we have test case set available and running these "test cases manually is time consuming. We know the expected results so automating these test cases is time saving and efficient regression test method. Extent of automation _ depends on the number of test cases that are going to remain applicable over the time. If test cases are varying time to time as application scope goes on increasing then automation of regression procedure will be the waste of time : Most of the regression test tools are record and playback type. You will record the test cases by navigating through the AUT (application under test) and verify whether expected results are coming or not.12-MTP-I Seventh Semester, Software Testing and Quality Assurance Regression Of GUI application: It is difficult oa ou (Graphica) y Interface) regression test when GUI structure is modified. he Ses wrten GUI either becomes obsolete or need to modify. Rousing t he noeression testing, cases means GUI test eases are modified according to new GUI. But this task egy? cumbersome if you have large set of GUI test cases. Example regression testing tools are: + Winrunner + QrP 7 * AdventNet QEngine * Regression Tester \ + V Test * Watir * Selenium * actiWate * Rational Functional Tester * SilkTest Q.1. () Explain Brainstorming. @ Ans, Brainstorming is a technique used to quickly generate a quantity of creati, or original ideas on or about a process, problem, product, or service. A brainstorming session begins with a facilitator establishing basic ground rule: and 2 code of conduct. ‘Typical brainstorming rules state that all members have an equal opportunity to participate, there is no eriticism or pulling rank, people should think creatively, no idea will be treated as insignificant, and there should be only one conversation at a time. Members need to be active participants, willing to share their ideas, opinions, concerns, issues, and experiences, necessary. Remaining ideas are then evaluated with a with the affinity diagram, nominal group technique, or cause-and-effect diagram, Q1. @) Discuss various Quality standards and guidelines in software testing: ©) Ans. Most products have safety standards, and many have usability standards, but computer software rarely has such standards, * Itis very difficult to enforce standards on * Standardizing the process can hel * Standardizing to an inapproprial leave less time for quality actual program behaviour| LP. University-(B.Tech)-Akash Books MTP-I-13 * A characterization that establishes allowable tolerances or constraints. for categories of items, * A degree or level of required excellence or attainment Prevents idiosyncrasy: e.g. Standards for primitives in programming languages) Repeatability: e.g. Repeating complex inspection processes Consensus wisdom: e.g. Software metrics Cross-specialisation: e.g. Software safety standards Customer protection: e.g. Quality assurance standards Professional discipline: e.g. V & V standards Badging: e.g. Capability Maturity Model levels Comparatively few software products are forced by. law to comply with specific standards, and most have comprehensive non-warranty disclaimers. However: * For particularly sensitive applications (e.g. safety critical) your software will have to meet certaini standards before purchase * US courts have used voluntary standards to establish a supplier’s “duty of care” ‘Terminology I Overall guide ae Principles and objectives T Element standards en ‘Application guides Tools and techniques. Adherence to standards is a strong defence against negligence claims (admissible in court in most US states) There are instances of faults in products being traced back to faults in standards, so Standards writers must themselves be vigilant against malpractice suits. : Q.2. Explain the criteria for test case selection and execution. (12.5) Adequacy criterion = set of test obligations: * A test suite satisfies an adequacy criterion if * All the tests succeed (pass) ; + Every test obligation in the criterion is satisfied by at least one of the test cases, in the test suite. + Example: the statement coverage adequacy criterion is satisfied by test suite S | for program P if each executable statement in P is executed by at least one test case in __ S, and the outcome of each test execution was “pass”. . z * Sometimes no test suite can satisfy a criterion for a given program =~ + Example: Defensive programming style includes “can't happen” sanity checks if(z <0) :LEMTP-1 Seventh Semester, Software Testing and Quality Assurance throw new LogticRrror( “z must be positive hor LP, University-(B-Tech}-Akash Books MrP-is , + Approach A: exelude any uns lc obligation from the criterion, + Example: modify statement coverage to require execution only of stat that can be exocuted. + But we can’t know for sure which nre eacentable! velopment environment for Selenturn temments + Terms: An adequacy criterion is satisfied or not, a coverage meamure ig the f orem caus fed oF not, e 18 the fraction 2 Support for Soleniam user-ewtensione joie 8. Q ENGINE ~ AdventNet QEngine offers integrated colutions io test and verity 7 Coverage is only a prony for thoroughness or adequacy the Atndenallty and performance ofboth web applications and web terviene, Features + Test wolection approaches " Facto: ficatlon-based critarion may suxgest test cases : tions of valuce eee Ceuite from specifications, then use structural criterion, 1 Scripts are written in Jython, an implementation of Python: Python scripts are the rource code fe oimple. eatured modern scripting language, rather then a propriotary, Powerful and ousy to use. utomates the functional and rexrenaion testing sega quality acmrance team teoc snore ofan ipplication in lose time.16-MTP1 Seventh Semester, Software Testing and Quality Assurance + Powerful, Easy to Use Scripting Language * Object-based Record and Playback Engine ss Integration with Seapi jonal Functional Tester ~ Provides testers wit ation ster ~ Provides testers with automa for func 3 repression testing, GUI tating and data a and customization. + Supports version control to concurrent usage by geographically distributed teams. GSpptorts custom controls through proxy SDK ava Net) (a) Explain the difference between static and dynamic testing tools) with example. Static Testing si Borie Hote ith automated capabilities for data-driven and keyword tes fers testers a choice of scripting language a rece eT & Choice of seripting language and industial-strength editor: Jaf" “sual Basic .NET® in Visual Studio NET for test a ve parallel development of test scripts a Dynamic Testing po 1s testing of without execu the Software. ee In Static Testing software are Static analysis tol wed Static Testing can slat erly in the lite eelegBy Vey User Requirements ‘Types of defect find in State esting are: Misting requirements, De defect Syntax Error ete 1ypes of State Testing: Review, Inspection» Walkthrough” Statie Testing find bug before you about prevention Static Testing done inthe verification, stage. Static Testing gives 100% statement coverage, Tes iatng that involves the ee of the Software, heat In Dynamic Taig aware executed by giving Dynamic testing can start after evelopment of software components. he code to guide the testing process, On a very high level he source code in sm loident worker to take a perzon: LP, University-(BTech)-Akash Books MMTPL-17 A. (b) Define mutant based analysis. eo ‘Ans. Mutation testingis a structural testing technique, which uses the structure of 39 process of rewriting sal ways in order to remove the redundancies inthe source code ‘Those ambiguities might cause failures in the software ifnot fixed and can easily ass through testing phase undetected. Benefits: «= It brings a whole new kind of errors to the developer’ attention. “ibis the most powerful method to detect hidden defects, which might be impossible ‘using the conventional testing techniques. « Tools such as Insure++ help us to find defects inthe code using the state-f-the- « Increased customer satisfaction index as the product would be less bugsy. {Debugging and Maintaining the product would be more easier than over. 25) de that the amount of mistakes ‘catch them before thay reach the Sct the worker directly, such a8 ‘Defects invelves reconditioning the ig he does(,]by convincing him that his fant as the task of the doctor or the den defocta means a defect love of infinity s “sn attitude toward process improvemer possible. ‘but the is just as import ‘Statistically, 2er0 ‘most people mean, i8 eering gets in the was: fan implicit assumption sro Defects” movement has aoe notte. In firms and products, defect ‘Types of defect find in dyn and the customer o are: Variables not constant Ieutpat fom the expected values. Types of Dyname Testing: Unie testing, Iategartion testing, System Teetiog Acceptance Testing. ic tstng find bug aor comp Jation, linki a ‘gates = ig does not give 100% work required t found. tector _thoroleotienterinsoftware developieat: aa ‘testing, testers should review sr oremen into rene aaa Fonments oF ass sey often setup tho tat emi sovork nanagerent stalin doin ee atoneation bein he a jlement tests: oftesters often inereases, starting with the and document problems 1 Testers execute and log the te vironment, oten sing tons fortis ask They monitor the testing and the test em oe ‘and often gather performance metrics. ——————‘ité~™1e-MTPA Seventh Semester, Softwere Testing and Quality Assurance + Throughout the testing life epee, they #0 troports and Lest results ie documents and understand what needs tobe tested, ‘formation procured in the above step decide how itis to bo tea dl abont what all esoures willbe required fr software eating 1s and prioritize testing activities. est se and report defect, define severity and priority fr gag ow each others Work, inching ty * Carry out regression testing 1e when changes are mada to the cx dag LAT out rerension tes every me when change ade to the code to Q6.(b) Define test scripts. 65) “Ans. Atest scriptin software testing isa set of instructions that will be sting is a set of instructions that will be perform onthe eaten under ter ta on Ut be eyien functions aseapected. ‘There are various means for executing test scripts. ‘+-Mamual Lesting. These are more commonly called test cases. + Automated testing: * Short program written in a programming language used to test part of the written using a special Professional, Borland ‘Programming language (such ns Crs, opranming language esha Cr, CHT, Exped, ave, PH, + Extens Perl, Powershell, = aramoterized short programs a.k.a. Data-driven testing usable steps created ina table a ka, keyword-driven or tablo-driven testing Step] twiacon | Bapeted | actual | Gommene fut | Rea 1. [Speuptie | Siena Wd Mixrosoft. Word ‘opens. fe trata 2 [eraeanee | a sev taka | Pax ‘blank document. ‘cument is displ- " a 3. | typo the fatowing | THe in ventence is | Pass sentence into the | displayed inthe document, ‘The word"bold"is | ase highlighted. 5, | Clicktnebotd | Thoword"bold"is | Pass Dotton onthe | belded top toolbar. : LP University (B.Tech) Akash Books MTP-19 Q7.Expl (@)_ Test case template for a company sales interface. as Ans. » “ Title Pre-Condtions ‘Test Steps 2, Enter the enstomer information. 3.Cliek "Ada": Expected Results ‘Armessage appearsin the program's | status bar, The message réads "New" customer added. cy Qi. (0) Quality of a good test ease. “Ans. Agood test case has certain characteristics which are: 4. Should be accurate and tests what it is intended to test. 2. No unnecessary steps should be included in it, 8. Itshould be reusable. ‘to requirements. 5. It should be compliant to regulations. 6. lt shouldbe independent i.e, You shouldbe able to execute it in any order without any dependency on other test cases. 77 It should be simple and clear, any tester should be able to understand it by reading once, ‘3 Now keeping in mind these characteristics you can write good and effective test ‘Pests onty one thing: Always make sure that your test ease tests only one thing, if ‘you tp to text multiple conditions in one test care it becomes very dificult to track results and errors, ‘Organize your test eases consistently: You can organite your test cases in many ways hevrever Jou should alrays follow the same patter to organize you test cases Write indopendent test eases: Your test cases should not have dependency on other tot casos, 2 yo! should be able to exccute your test case individually with having {Copendency on other test cases. ‘Write small test cases: Always mention purpose ofeach tet case clearly in test Define Testers. @ software tester is involved in the quality assurance stage of software evelopment ané deployment. They conduct automated and manual tests to ensure the oftware ereated by developers fit for purpose, Software te fof soflware, and systems, to avert risk and prevent software ‘wster is integral to the ereation of softwe technical produ ing vehiles,cleetronie goods, defence, and healthcare Ullimately software testers are employed to find bugs and iasues with before it gets deployed to everyday users. They can work on bespoke indi1 Seventh Semester, Software Testing and Quality Assurance sects spanning the globe and costing be familiar with progearnm [Assessing code is one part af the ole of software tester ser cna vary depending on project entation stages 2 ass OF be eth ben esting becomes a Key requirement, Jers dedicated 1 one project; whereas king on multiple projects, ions may have software ts ‘may have a central team Wo * Meeting with system users to understand: lanning; itoring applications and software systems; 5 testing; + Performance testing: + Functional testing, + Scalability vesting; + Writing and executing test seripts; + Running manual and automated tests; + Testing indifferent enviroamenta including web and mobile; + Weiting bug reports; + Resource planning, + Reviewing documentation; + Working towards departmental and project deadlines; * Quality assurance; + Providing objective feedback to software development project teams; + Problem soli 38 Seaingso sofware development and busines user teams to it project sites; " teams in other parts ofthe world; ings to technical and non-technical colleagues, MODEL TEST PAPER II FIRST TERM EXAMINATION SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE (ETCS-403) Time.1.30 Hours MM, 30 is compulsory dnd attempt any too from the rest Q.1. (a) Bxplain contro! flow testing. is a structural testing stratogy that us ol-ow testing techoiques are bared on. Controllow testing is most applicable to new software for unit testing. Control- ig assumptions: ~ specifications are correct ~ data is defined and accessedcater Software Testing and Quality Agsurance vena LLP. Universty-(B-Tech)-Akath Books areas ecuted, who executed ‘These descriptions are -MTPAT Seventh: ‘Test contro asthe fl Te mamure and analyze the results ofreviews and esting ‘To monitor and deeument progress testcoverage and exit criteria To provide information on testing sp intiate eoresive actions. (0) Tomake decisions ; (2) Analyois and Designs Tes analysis and Tet Design has the fllowing maj tasks: (To review the test asts (The tse ing major task: Dut, whatare the test cases that we executed, in what orde ‘status ofthe test case (pass Compare actual resul!s re differences between actual and expected results, it report 4a and Reporting: Basedon the risk assessment ofthe project we will set the eri zainst which we will measure the MCnough testing”. These erteria vary fom projectto project and are known as ext criteria, Exit criteria come into picture, when: “Maximum test cases are executed with certain pass pereentage. + Bug rate falls below certain level. + When achieved the deadlines. aetna wgexit eriteria has the following major tasks: "To check the test logs agains the exit criteria specified in test planning. assess ifmore test are needed or ifthe ent criteria ecified should be changed. fo write a Let summary report for stakeholders. ‘Test Closure activities: Test closure activities are done when software is ed. The testing can be close for the other reasons also like: + When all the information has been gathered which are needed forthe testing. + When a project is cancelled. "To evaluate testability ofthe requirements and system. - To design the tet environment set-up and identify and required infrastructan environment and any other test infrastructure. (Tea asta et ofcondions under whith eter wil determine whether an aplai + When some target is achieved. isworkingeorretly or not). + When a maintenance release or update is don. term for all uilities that seve in eombination for testing a softwar ‘Test closure acti er tant nfrantruetaro for later renee.) ) Tocheck which planned deliverables are actually delivered and toensure that all ident reports have been resolved, testware such as seript, test environments, ot. for to the maintenance organization. ‘They will give 1g went and learn lessons for future releases and projects Q2. (a) Explain deployment testing approach. @ oftware and test data for tests : for testing a progra 1nd monitring its behaviour and outputs. © test cases for efficient test executio tare used to testa software pr ts us sete loyment testing is testing the application afer itis installed on the system, din tobe used during testing. Test suites are used to group. Difference between black box and white box testing (iti) To implement and verify the environment. Black Box White Box ‘Test execution has the following major taskt Testing Testing ‘White box testing in the software testing method in which internal structure is being known to tester the internal structure ofcodeor | whois going to teat the software, previ lender wenn known as confirmation testing or re-testing. Condesa] oo Centon] “ THE eon | oy N toot | N Ser Sate to “ar y 2:0) What doyou mean vont youmean hy sofrare quality quali aparece and qual re Grin Definition and evaluate the luce products, LP. University-{B-Tech}-Akash Books 2016-3 Focus Process focused Product focused Orientation | Provention oriented Detection oriented Breadth Produet/projoctepecific Scope Relates to specific product Reviews, Testing not possible to test in automation testing. If sunderstanding of company processes: ould only go with company processes ‘corrent testing scenario, This results sting work simply becomes ty changes, previous working ig always under time constraint: that you need to complete within specified time. This i test cases. a source code complexity measurement thats being fated by developing a Control Flow jependent paths through a ity, ower the risk to modify and easier to low formula:‘Soventh Semester, Software Test 42016 P 3. (b) What do you mean by Boundary Value Analysis? Explaj, i applicability. | ‘ PHA value analeis (BVA) isbaeedontosting at the boundaries btyy | pans Bee bth valid boondaries (i the valid aTEtions) and ing [otnarie Gi the invalid part - For example, consider a printer that has an inpat option umber oe made fretn 1 t0.99,"To apply boundary value analysis, we will take the mini ee ae eas rom ine val partion (1 and 99 inthis cise toga aa ihe tae or nat value respectively in each of the invalid partitions adjacent ta valid parti {this example we would have threo equvatges Haare tane fom eave the three partitions) and four Boundary Value aga Qu, (a) What te lovel of testing?Explain Unit,Integration, System gq) Acceptance Te | ‘Ans: Unit Testing | ‘hin type of tenting is performed by developers before tho setup is handed ove the ening Loam Lo orally exeute the test nse. Unt testing is performed by | ‘eapective developers on the cource endo assigned arcan it Gvelopors ure tat data that i diferent from the test data of tho quality assure ‘eam, 51 of unit testing is to isolate each part of the pre individual parts are correct in terms of roquirements and funeti “esting cannot catch each and every bug ia an application. It fs impossible evaluate very exestion ath in every sftrareapalcaten The eames thease sting “There is a limit to the number af ecenarios and test data that a developer can we toverifya source code. Aer having éhausted all the options, there fe no eholce Btls stop unit testing and merge the code segment with othr uit Integration Testing Integration tastings defined as che testing of combined part of an applic ing ofcombined parts ofan application determine i they fanction correc ntegration tstngcan be dane In io ws Bote ‘up integration testing and Top-down integration esting ae Bottom-up int sting begins with unit testing, followed by testa | oer inaions oot caled modeles han own ing the high-level modules are and ropes lode rested tereater ns” we est Ina comprehensive software " preferably in scenarios designed to mimic actual ations. done first, f components are integrated, wets the specified Qual! Acceptance Testing: ed testing team. ‘This is arguably the most important Quality Assurance. Tes porrant Lyre of testing, as itis conducted by ‘hethér the apy ‘meets the intended ment. Tho QA team will have a set] ing and Quality Assurance * | . LP. University-(B/Tech]-Akash Books 2016-5 Acceptance tests are nat only intended to point out simple spelling mistakes, cosmetic errors, or interface gape, but also to point out any bugs in the application that ‘tem crashes oF major errors in the application. ;ptance tests on an application, the testing team will deduce how erform in production. There are also legal and contractual the application ints for acceptance of the system. vols of testing include different methodologies that can be used while conducting software testing. The main levels of software testing are: 1. Functional Testing 2. Non-funetional Testing. ‘Functional Testing ‘This a typeof black-box tasting that i based onthe, specifications of the software jut and then the results system's compliance with ite specified requirements. "There are five steps that are involved while testing an application for functionality. Steps Description 1 "The determination of the functionality that the intended application is meant to perform. u "The ereation of test data based on the specifications ofthe application. ig involves t “ ‘nature but important such as performanee, security, user interface, Examples: Performance Testing, Load Testirig, Stress TestingRM EXAMLNA2IU++ rs erty BN EVENT SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] ‘Time:3 hrs. | Note: Attempt all quesions as directed, Interna choice is indicated. Qa ) What are the building blocks of total quality management, ‘Ans: A coro definition of total management (TQMD describes a manage ‘apprench ta long-term success through customer satisfaction. In a TQM eff suambers of an organization participate in improving processes, products, servi the culture in which they work. (a) Ethics. Nb) Integrity. © Trust, (@) Training. (©) Teamwork. problems carly in the process. known as “testers”, "he differen that QA ie proseu oriented and QCis therefore is predict oriented ana thue ig in tho QU domain it's controlling it. Quality Assurat ieee iy, ontraling it, Quy Ansrance maken ure ow ate dln measures of software quality : The sy sel under given cos cing Mean Timo Between serene fame Ato Io averepe Combined with Mean Ripe Fale te San be sed to alate MODE hate lean Time To Reps after a failure occurs. MTBF can be| (TTP), whieh describes how long the softwar] MTBF = MTIF +. 2. Correctness: Anyatomor ntware mut hea ne defined as the d fiware engineering, softwar ing activities. Maintainabi 1 software product can be modified t requirements, to make future maintenance easier, or adapt to the changed environment. inability is assessed by using indirect measure: pensive and time-con: ntenance is one of the most an be defined as the eae ‘Mean, ‘all users. Generally, it has been obeorved that programs having lower MITC are: to maintain. 3. Integrity: the age of cyber-terrorism and hacking, software integrity has ‘become an important factor in the software development. Software integrity can be defined as the degree to which unauthorized access to the components of software (program, data, and documents) can be controlled. For measuring integrity of software, attributes such as threat and security are e probability of a particular attack Integrity = 3/1-(threat*(I-security) Jhich is easy to understand and easy to use is always tobe inderstood, learned, ani ‘ccomplishes all the user requirements but is not easy’ to {In addition to the afore-montioned measures, lack of conformance to software ‘ements should be avoided as these form the basis of measuring software quality. ) Why is functional testing also known as black box to: help of examples. iy nt tes fs « quality assurance (QA) process and a type of black-box Geatione ofthe software component under 1 ethod) of your ystom. ) What is scaffolding? Why do wo usestubs and drivers during unit ‘Ans: Scaffold mota-programming method of building database-backed isa technique supported by some model-view-controller frameworks, it application code that the application can use to create, effectively treating the template as a “scat application. ‘Those dummy pieces of eode are the tubs. On the other hand, Drivers are the onea, which are the “calling” programs, Drivers are used in bottom up testing approach.sonvare Testing and Quality Asrurance ter, 2016 Seventh Sem athe sub modules are ready but th, Drivers are durumy code, which ib v8 EP, Univeraity-[B.Tech}-Akash Books 2016-9 he testing we integrate the different modules and test the interface between them to check produ ail ot ready sare always cstnawish as “alle program\ | he dal Stabe are day snl 2S pdm ano wad |, What scents youcarey ta andl ini . ‘Ans: Scenario eating is a oftware tating activity that uses scenarios: hypothetical programs areunderconstuslO™ form of dummy modules which are xjes to help the tester work through a complex problem or test system. The ideal Drivers aro also considered a= TROT led in bottom up integration nario tosti a credible, complex, compelling or motivating story the outcome of which stinguled galing rams ore wer construction only ved when ain PC saint ans a measure of quali 3, data-driven approacy tnethodology fo dina dard deviations ety the mean and the ne any process ~ from manufacturigg transactional an from product to serve ‘he statist roprsetatin ofS Si sere their actions and objectives 1cker’s mindset and list possible scenarios of system it the system events and how doet the aystem handle such requests, benefits and create end-to-end tasks to cheek ther, igsa describes quantitatively how a prea | systems and their behaviour. oe must not produce more than 3.4 def defined as anything outside of customg erunity is then the total quantity of chances f Sipma ean easily be caleulated using @ Six Sigma calculator, ) What is the purpose of Automated Test tools. “Ans: Verification is the process of evaluating products ofa development phase to pecified requirements.The objective of Ve ‘an essential component of successful development projets development orgat smaller companies ta implement. SmartBear's Tools are affordable enough for sing falkthroughs are informe, initiated by the author ofthe sw product toa colleague for assistance in locating defects or suggestions for improvements. ‘They are usually ins the product; colleague comes out with observations and + Person who originally ereated the work product. rator Person responsible to ensure the discussions proceed an the productive ents System testing isa type of appli aye yal interfaces. Th system testing comes under bak fe code is mt of softwar a = Recorder: Person who recordsdocuments all the defects that ariso from the nspection team. = Inspector: All ofthe inspection team members who analyze and detect the defects inthe work product. = Reader: Person responsible for reading aloud small logical units of the work iT it meets the spec duction data is not used in this test data a ‘type of testing. In system integraio™‘Seventh Semester, Softwa 10-2016 sofa product for the PUTPO30 of m, saminati oi Review isa gubtequont examP0T ore persons check the changed q sin hich ane ‘an analysis, cari changes. ee press TES caret. bie also an analysis under or data to determine ifthe chang. to which stated objectives have been, fixed point in time to determine the {Q2. (a) Explain the software Dt assurance. roces that ensures tha wuality assurance (SQA) is # F I To tury ug a one tions {Sam cnoing proces within the software develope i checks the developed software to ensure tps ensure the development of high-quality software: SQA prag sag thr came tere yet earl fC und implemented i st os Sancta and inlet sotiodngee ot steal ete gly mech peo sansa tea 1s phas ‘Ans: The’ aserash, bomb and abend. Failures can alto be caused because of the other reasons also like: ‘radiation burst, isin hardware or frm ecllon of nivare " alle my i are bene of human era in narctng with he wa perhape a wrong np ale being entered or an ouput bing misinterpreted i Deadlines, eg. release deadlines, testing deadlines; Percentage of test cases passed; () ‘Test budget and rate of spending (your burn rat i ing Qour burn rate and the amount ofrunway# (4) Amount of code, unetionaity, or requiem Ce iol requiem ecard (6) Duration ofteta or alpha eat ng periods 93.0) Whats the diference between sting nd debugging : Debugging is conducted bya poy Ei don pausing conducted apogramner and th programmer fx to prea Phase. Testers never Gx the eros, but rather fined them ad acess with respect 10 software a ‘evelopment ntl thet rave press moves into the nex pea ity of program to continue processing due to erroneous logic Sf wre Testing and Quality Assurance 4 LLP. University-{B.Tech}-Akash Books 2016-11 ‘Testing Debugging always starts with knovn uses predefined methods, and has predictable outcomes to, 12, Testing can andshould definitely be planned, designed, and scheduled It proves a programmers failure. 1. Debugeing stare from possibly un-know} 2. The procedures for, and period of, debugging eannot be so constrained, 8. Itis the programmer's vindiation 4. This always treated as a deductive process. Itie a demonstration of error or apparent correctness. ‘Testing as exeeuted should strive tobe predictable, dul, onstrained, rigid, and inhuman, ‘Much of the testing ean be done ‘without design knowledge. It must be done by an insider. 5. Debugging demands sposeble without detailed design knowledge. 7, Tecan often be done by an outsider. 8, Automated debugging is til a dream fr programmers. Much oftest execution and design can be automated. ‘Testing purpose is tofind bug. __|9. Debugging purpose isto find eause of. reduces the long term costs by making iteasier and software changes. long-term cost of software by reducing the cost of validation This fanction manages the poicioe for improving the res funstions, and also sets and disseminates the mid- ets. -ance Organization: This function as assurance, organizes Quality Revi and manages organizations to promote quality assurance. '8. Quality Assurance Education: This function educates all employees about ‘and improves employees’ problem solving skills through special training targeting corporate officer to tings, and establishes 4. Quality System Standardization: This function establishes and disseminates common rules, and also organizes disseminates, maintain, and improves the business for each business or the product characteristicssoftware Testing and Quality Assurance Seventh Semester, ction confirms whether the work py Nate bow oe LP, University {B.Tech}-Akash Books 'DD Graph for the given 4 Construct question and also Complexi ‘Ans. # ineludacstdia > Hineludecconio.h> nt main © i inta,b,¢, boolean = print{ nt Enter side-a seanf (ed, & a; printftnt sean Cha", eb) a > 0) 2K (a-<- 100) (b> 0) BE (DI (¢a)>b) &A Ub +e)> a0) Kk (o> 0) Ke printf ("Triangle is equilateral”; ' elseif (a==b) Ib==0) 1 print (Triangle is isosceles); se | print“Triangleis scalene); 2016-13satware Testing a8 Qual Aguas. ike this: des inthe above low graph, yy LP. Univesiy-{.TechAkaeh Hooks 201616 soveem goa dee oy uation 1 from intervs oventh Semele her as a single reat the loving DD Pal th Graph Roots are real if(8* ~Aae) 20 Roots are imaginary iN ac) <0 Roots are equal iff? ~4ae) =0 Equation is not quadratic fa =0 ‘Total numberof Test eases =4n+1 Wheren -»numberofinputs = A(3)}L13Test eases Boundary value test cases are given as: ‘estCase a 6 e Expected Output 1 ° 25 25 ‘Not Quadeatie 2 1 25 25 eal Roots a 25 25 25 Imaginary Roots 4 “9 25 25 Imaginary Roots 5 50 25 25 Imaginary Roots 6 25 ° 25 Imaginary Roots 1 25 1 26 Imaginary Roots 8 25 9 25 49 Imaginary Roots 50 Imaginary Roots ; How are surveys helpful in post Caleulation of Cyclomatic Complexity V(G) by three methods O-n¢2V(G)=28- 18+ 2254207 MiG)=P 41 G4157 (Nodes ,¢,g,h, ,j & nate predicate nodes with 2 outgoag ia, my documents, local settings, appl 104: VIG) «Number enclosed eystem, (Here, 2,85, pus regi 18 4122, Survey quest ee FA, RS & R6arothe enclosed regions and 1 correspetll portant wi VG) =7 anda sa how businesses gered sells 1e three methods, from technology, busi cris arora ‘While th ruil Ueir teams and adopt eauationitsinpatic wipe ne nature of roots of « 484 eae ere eon ile of postive integers: formance cogincerag culture, they show a fei amount of agreement on the core erate lowing wort "Meera Inter a ee te hanes el eieranr in Wa nk nae se ati equation, Real roots, Imaginary roots equalreo# Da under the performance engineering umbral oe fat Sing tn ne Pec "forthe determination ofthe nature of roots of ast] POSNANSSseventh Somesten, Sofware Testing and Quality Agusan. Sa panther words, yerformene eninecring tant, In other ore that ive working omooane Sa ee ey wonton ee a LLP. Univorsity-(B.Tech]-Akash Books 201817 lly management system under which the software aystom le created 13 sod on one or more of the following modaluurandards ger ee aes na ites SSB i aes OC ang sellers cee cs pore sar msee osatgurtte! Meaemestisceses TM camine sz ano Sette Cone wii at ae Sete a sxe gel oy pets a ioe na nck chao In software engineering, ie inate waste and inefficiency, thereby increasing ‘delivering what the customer ts expecting: itructared mothodology, and has defined roles for the se nar and discipline required to tise those tole propasly. ‘Explain how software quality assurance is ensure fA sot of activities for enmurin ely rooultin quality in softer voces definition ad limp eating stware Development Methodolog Project Mi “e nts Developmen’ Management, Estimation sve been defined ln wa {And implemented, Quality Ascurans‘testing and Quality Assurance 18-2016 Semester, Sofware 3, Accuracy : Precisions of comput 4. Completeness: Degree to which have been athioved. mmmunicativeness : a Base with which the inputs and outputs can hg the source code, in terms of lines of code. {gn and implementation techniques. Use of standard data representation. ogres to which eontinuity of operation is ensured under #Compactness of adverse conditions. 10. Execution efficiency : Run time efficiency of the software, 11, Expandability : Degree to which storage requirements or software functions can be expanded, 12, Hardware independence : Degree to which a software is dependent on the ase with which the software can be understood, h, and energy, “tees as possible to perform its | In other words, integrity refers to tl | _ onal tera 5. Use nd attacks to ite security. which access to software or data by be cantrolled, v8 ‘A sofeware in considered to be utube human user thout a good user interface a soft me smuniinaut good ue Rovare system may fz LB, University-(B-Tech)-Akeash Books 6. Maintainability: Maintenance ef elas th uphogp of produce in enponee od components due ta continuous urcofthe produc meron fo deterioration oftheir Maintenance refers pect tai fers to how easily and inexpensively the maintenance tasks ean be 2016-19 || ____ For software producte, there are three categories of mai net |] corentive, adaptive and perfective muintonance: fT” mumenance ackiviicn | "7. Testabili ‘Tostability means the ability to verify quire hi nee areata At every stage of software ‘necessary to consider the testability aspect of a product. ‘9. Portability of a software system rofers to how easily it can be adapted to run in a ime to develop and test the component being reused. {thor oF not the output of ene system is acceptable an iuely that the two systema run on different computers, ted by a network, 'Q.2, th) What is z0r0 defect movement.Discuss various key process areas of CMM at various maturity levels. oo! aimed at the reduction of defects through ‘people to prevent mistakes by developing a Ssrright the firet time. — Zoro Defocts: A New ssclous desire to do the Quality Assurance. eeesatnare Testing and Quality ASCurang st enti te canes defects me tT identiy Bena new techy 2 improvethe process toimprove quality | inva impeore naa isto continually improve the gay | ena of proving soya cyde time for product developmen eae roved for normal practice, the organi, ingen save proccss ara eatware process i Standard eaftware process an tuted. ‘Thegoals sought! Carino process improve he organiza! toachieve areas follows! sment is planned: | q ins software process improvement sett | Participati to perform bara MF SoREWare prow The oe tepmrenen / ynior management sponsors the organization's activities for sofware prog mpl pea ranepion beens: are provided for software process improvence| actiities Softsare managers receive required train ‘The managers and technical staff of in software process improvement. | Below Poor Annual Increment depends on the earned. Gonorate test casos sa ‘ulvalence clas testing and decision tale ‘Ans Tho cases generated on the basis of co class Testing we: | sasia Excl 19.47 ees GOsx55, a on Average Yeor LP, University-{B-Tech]-Akash Books 2016-21 Test CaseNo x Expected Output 1 10 Excellent 2 85 Very Good 8 19 4 4 5 6 6 “1 1 i Iowalid Input ‘Test Cases on tho basis of Decision Table Based Testing ‘Test GaseNo |X View Expected Output 1 | Excellent 10% increment 2 87 Very Good | a 6! 1 a gostraon. he generator wil gonerate rctristies ond bvedon what the weer tne. Toa Kind of toot Databases SQL Server DB, Oracle, ‘SQL Server, DB2, Oracle, MS access GSApps Upscone InterBase, Fiebied, Productions MySQL. Rodale MS SQL Server Oracle, MySQL, BS SQL, SQL, D2, Fircbind BMSExports insrt er your database. Pee wis dynamio test data generation tings the p tulomated reviews of the documents, This review ng W catch defect early in STLC, It examines wok (6) Test Cases lei LP. University-{B Tech}-Akash Books 2016-23 Seripts ‘or User document ting, code is executed. It checks for functional behavior of ‘omory/epu usage and overall performance ofthe systera. Hence tbe testing is to confirm that the software product works in juirements, This testing is also called as Execution tes the output with the expected ‘outcome. Dynami testing and it can be either black Scenes ae : = = ; : reat] [nttow | [Pa Q8. (©) What are the categories to evaluate regression test selection technique?Why do we use such organization. Rarer oe a Pocrtzaton of "st Cases, for regression testing in which all the tests in the ld bo re-executed. This is ery expensive as it requiresand Quality Assurance 24-2016 ‘Seventh Semester, ‘Software Testing Q " FIRST TERM EXAMINATION sim beter to ablee rt tat [SEPT. 2017] ite, nu SEVENTH SEMESTER [B.TECH] Pe egeanctegeaes Resale Tsk C80) ODT SOFTWARE TESTING AND QUALITY ee ctu ASSURANCE [ETCS-403] sate tere canbe ein suse taalncne oe ied Note: Qia1iscomplion Attempt any 2 questions fom terest. fest Cases | mbusinessimpact, critical & frequently wag | @4+Define the follow cs depending on b tly reduce the regreanes cyeles. Timer di hrs, MLM. 330 Example: Consider an app characters, ce, there are 25 * 26 * 26 input iphabets only: Including special characters and standard charaeters, \uch more eymbinations. So, there are 256 ° 256 * 256 input eombinati Unit Testing. respective di developers use ‘data that a developer can use to verify a source code. After having the options, there is no choice but to top unit of test eases may also contain prerequi following tests QL. (d) Limitations of Testing. @ ‘Ang. Testing Limitations You cannot teat a program completely + We can only test against eystem requirementssega Qtr hove me care Testing nd OM LE Univisity {toch Akash Rooke sis knowledge to develop test. ay ead atest ring a aed 22017. Seventh Semester 5 aii | May nt dete errs in th = Incomplete oF ‘ambiguous rea . « sotein pete cena. ant ta spd eral Hanning be ‘© ‘Time and budget constraint ‘cases that will examine the control fo ¢r7or handling as well as coding practices eed and budget rs decisions for release dates, run out of test eases ‘run outof tie before 3% test every path, C Refer Q.1.( ¢ Term 2016. 2G Eaplaia the Boundary Value Analysis with the help ofan exangl ter analyzes arid understends the structure ofthe system by examining ct lor 3.8 Fint Te 2018, A re panrane Quality Conroinermsot Say rea ‘The tester‘ understands the weak spots within the code that is most prone to a Dieters et eo sven datftematin! onl ows 2, (a) First Term 2016. so de Qs. Q3. (a) Black Bor & white Box Testing ofthe int Tests: Al tho conditions in a epecifc deci and data that are used ‘through each possible ‘Testor aloo includes some negative test cases with invalid inputs and expe ‘outputs (error messageslorosram termination) as applicable. q ‘ondition Tests: This will ensure that each point of entry with in the Techniques Box Testing sastonce during the testing life cyele ) Cyclomatic Complexity & DD-Paths 6) complexity measurement that is being alculated by developing a Control Flow inearly-independent paths through @ Graph ofthe code that measures the program module. ining: Inthe identified along with its corresponding “ sponding validand invalid Ths approach an at dentin a Tis tors ldentiyng dats fearon ‘Lower the Program's cyclomatic complexity, lower the risk to modify and easier to ‘understand. Itean be represented using the below formula: + Brror Guessing Cyclomatic compleity =B-N+2°P wang eae and fi sunarsnced tester most often uses this approae> where, White Box Testing: In white bevtecey est eases. ‘Es number of edges in the flow graph. ofthe internals of a s} esting met ‘= number of nodes in' low gra] sernals of lem and kaon bow the sy ey a a oe . ‘Ne number of nodes in the flow graph.testing technique invented by Kaoru Ishiks 4, (a) Explain Cause’ Effect Graph eral path is defined aa pai i ‘emanates either ‘entry node or a deeision ieeper ata decision boxor at an exi, th excopt those at both ends aphing Technique a "Shows the connection between a gi, aly show (go Bit Graph walle he outcome Sram because of the way ila ‘agra Effect — Flow Diagram eft cause ‘most important type of testing, 981 zmwho will gauge whether the application the client's requirement. The QA team. {Vand cont END TERM EXAMINATION [DEC. 20: . 2017] SEVENTH SEMESTER [B.TECH] SOFTWARE TESTING AND QUALITY ASSURANCE [ETCS-403] MM. 75 Note: Attemptany five questions including Q.no.1 which compulsory at should wo Tost? Discuss te areas which should be focused on durin a wo “Ans. Basic functionality testing. Begin by making sure that every button on every Q.1. (6) Find the test eases which coverage, and branch coverage for the following code. it(>=0) print( Message Y9} elxe print(Mossage not ¥:)] ‘ane. We want to oxecute every natoment ofthe program inorder to achieve 290% ee ee eee Consider the flowing portioa of source code along with {tt program graph given in Figure. fincludecstdio.h> Hineludeg-2017 Seventh Sernotter, Software Testing and Quality surance void maind { inte,be2=0,9=05 lreer . printftBnter three numbers”) scant“ ed a" a, &, . (eet) Rare atari"; ee serene 33, printi(x= Sd y= %e"y59) 14. getecho; 15 1 ‘The objective of achieving 100% statement coverage is difficult in practice. A portion ‘of the program may execatein exceptional circumstance and some conditions are rardly possible, and the affected portion ofthe program due to such conditions may not execute at all Branch Coverage ‘We want to tectevery branch of the program, Hence, we wish to test every “True! and ‘False’ condition fo the program, We consider the program given in Figure. If we elect a=9,b=8,c=7, woachiove 100% statement coverage and the path followed is given as (a true conditions): path= 1-15 ‘We also want to select all false conditions with the following inputs: the path followed is four are sufficient to guarantee 100% branch coversee. ‘The branch coverage does not guarant a The branch cove S not guarantee 100% path coverage but it does guarantee Tren fal en ea on pire aoc hut ha crate = LP. University-(B-Tech,J-Akash Books sort Bio] Pathelds | Paths Inpute | Expected Output _ [awe x | paths-1 | 1-7,10,13-15 [7 8 9 | acoyeo 2, | paths-2 786 xe0ye-15 3, | pathe-3 978 x=130y=0 4. paths - 4 987 = Mb y=17 ‘Some paths are possible from the program graph, but become impossible when we ats a8 per logic ofthe program, Henc, some cabinations may be found tbe le to create. What are the measures of software quality? period of time or for a specified number jean Time Between Failure (MTBE), which 2, Correctness: A system or software mst fneton correctly Correctness canbe epre o wich snare perfessit pete function. Iteanbe meanired Semon defects are daunted over @ ‘expensive and time-consuming. with which a software produc thas been observed that p o ago of jhertorrrim and hacking, software ines Tae a ae Swaredovlopent, Software integrity can be neat ders to te somponents of eotvare beeen vers atten uch stron ascurty ar se winty ah patcalratiacest a given pene 8 Yat ivecare Using these ro atte, atlowngeqoation sy to understand and easy to use i always 4. Usability Softwate, which is eusy lp sneer ality ofthe covare to be preferred by the user. UsabilLP. University-{8,Tech } Akash B software Testing and Quality Assurance sparen Ds ime Nett ts ag | tm st war ea soniranon wn i ae an ding? Why do weuse stubs and drivers during uni, folding 2017-9 begina with unit testing, followedby testsof ations of units called modi i meats are integrated, thea fs the apeciied Quality Stan team wo. On the other hand, Driver ar the one, Fae Toareet Wimrvargued ntuien up Caling approach ye} uscd when heaub modsles are ready but the main modalts arious kinds of functional testing? Briefly nal Testing individual unit ‘i different from the Logical errors can be defined as— ing and Quality Assurance 10-2017 Seventh it where the syntax ia perfe ste a statement W fet Sometines, « proanme wil wee cbjet ede correctly. Hover, rs translate Uh eoUF® iven when the program i rn be quite hard to spot rogrammner wrote tis: Monthsin} 13 stir: . con ntti pepe feo emp ee a) ; sok init se et ea Logic errors, lea called Dues eet ged by meticulous program debugging. This ‘or desired result, Logic erors or ives, in addition to the traditional debugging routine, cane an ongoing process at istomer feedback after official release, is of a program is too large to be completely used in testing a eystem. There sre both valid inputs and invalid inputs, ‘The program may have alarge number ‘There may be ti onthe inputs, that i an input may be valid ‘An input value whieh is valid but is not properly timed is called ‘The input domain of a eystem ean be very large to be completely used ‘Ans. Tostng isa process rather than a singlo activity. This process starts from tet planning then designing test cases, preparing for and evaluating status till the teat losue, So, we can divide the actives within the fundamental test proses! wing criteria and Reporting (8) Test Closure activities LP, University-{B.Tech.J-Akash Books 2017-11 ‘and Execution: During test implementation and execution, we ‘test cases and procedures and other test ware such a3, the test environment and any othor test infrastructure. (Test ions under which a tester will determine whether an application er not.) that serve in combination for testing a software test environment and any other test infrastructure for later reuse.) . To develop and prio data fo for ‘We also write some instructions for carrying out the tasts which is known as teat procedures.LP. University-{B.Teeh Akash and Quality Assurance Books ncsoxt— Sevoth Semester, Sotere Tang and Gualiy are requirements being defined at the proper level of on findig deci in reac setae Teens th ih eqn ee norco tre ehers rch an ips ah Quad Caeser eager required for successful software development. — i cave desienTchniase foodie Tectcanedeen Tela stare engineerin iat on penton or Hat boxe UNIT-I1 an example of grading the students in an academic are marks of three subjects In the range of [0,100]. The to the following rules: 1 ‘Marks obtained ‘+ Equivalence Partitioning (EP) ces. 80.100 Distinction 60-79 First division 50-59 Second division 40-49 ‘Third divisoin + Statement Coverage O86 " + Branch Coverage Fail + Path Coverage (@) Generate BVA and Robust test cases + LOSAJ Testing wo wo wo joundary Value Analysis (BVA) teat eates forthe program determining the nerate test cases using equivalence class testing technique, Q3. (6) What is Quality Assurance? What is the right time to commence the wvelop a decision table and genrate test cases. ai a student TestCase | markl mes sais — ; ; B Py Fail : : a 50 Fail : to 0 so Second Division a so a si First Division : ae io 50 First Division 6 50 ° 50 Fail 1 50. 1 ee mt * ° te a First Division a ° = a First Division 10. o = 4 _ = is ° a a Fail ts ° a a First Division o = Se ne First Division van Hee enna athe proces dfined and ndards pinent are examples, A of QAactivities. A QA reviesti 14-2017 Seventh Semester, Software ing and Quality Assurance in are given below in the Table:- Output domain test eases marke [marks Expected Ou o 85 First divisi |e 8 5 Second division a 46 ‘Third division es 25 Fail * 50 Invalid marks LP, University-{B.Tech,}-Akash Books 2017-15, ‘We may have another set of test cases based on input domain. 1, = (0 smark1 < 100 and 0 s mark? s 100 and 0s mark3 < 100 | (All inputs ere valid) 13 is valid) }00 and mark <0 and 0:smark3 < 100) (markt is valid, marke ‘mark2 $ 100 and mark3 > 100 } (markt is valid, invalid) rmackl > 100 and mark? > 100 and 0 s mark8 s 100 ) (maria is invalid, snd marks is vali ; and mark2> 100 and marks > 100) (markt is valid, mark2 valid) yg (0-Smarkl s invalid and mark3 Pendime ioe ima 1 {mark1 100 and mark’ <:inp inputs are shown by a given in tet and 22. There are 11 impossible test cases out of large number and number. . Limited entry decision table Tr Ths 2 tte nt Prrrrrrrr baer 6 Input domain test cases . lPrtrrrrr rare are re rrre aa | mak ask | Expected Output Preatrrrrrrgrrrrsert Test Case = Second division tee Perrrrrerrararrrrartt 1 80 a Porrrrrarrrrrrrtret L a a SPrrrrrrrerrrrrrts i 50 a -trevrrererrereere i 50 fs litre rerrrtrereeee t 101 ‘tere rteetttrere i 50 Trreprererertee 5 50 -TPl ere. te ’ a Com mE ke dha tt 1 : 0 siloniteas x - a: Pint avin 101 sittin 50 oP tn 101 a: Beant en a shi sien 101 aero * 50 toe meee ee oe oe 8 0 tenia ‘There are 22 test aes corresponding to each calian inthe decision table The test q -1 Invalid mar 1) canes are given in Table, 8 : ra ‘Table 2 Tet osier ofthe givenpreblem z 10 ‘Tost Case | markt | markt’ [mark | Expected Output e - 1 = 50 50 Tavald marks a 2 101 50 50 iy 3 50 “1 50 ig Tavalid marks : 50 301 G 101 Tvalid marks : st 50 [& 101 Teva mark a ie oe Hence, the tata numberof equivalence class lest cages are 27 Gnpat domain)#6 || 7. ? : doraain) whichis equal 33, Mi 2 r (6) De ecision table and generate test eases. as }| § ; : ? This problem can be solved using either limited entry decision table or extend 1 1 ? ‘mpossible sara ren lietvenes ofany olution ia dependent upon the eeatonel | | 10 2 e oad ons. Thelinivdentydeclson abe gen tn edie f |. s = aii ity Assur LP Uni y seventh Semester, Software Testing and Quality swurance vereity-{B.Teth Akash Books Here 2 suerte cr eon eae 38-2017 lcm be pl a : 3 pid eae hs nex ee econ rn a td nated ? "i aperaloe! f RAK, mark and average value Incolumn6, rule counts S because rt 7 : ont caoherwn ts loving connate 45 4“ : « | 4 ? 1,m1,08,01 : : ? D2 5 55 5s a : ; oc ? oe se i a6 ss DS = a | areal ent ca ton ae “| ' : mm a B,C, ee rece or exe eo 2 eee ne sapere ios wean re jan product of number of equivalence clanses of entries having ‘do — (0 fineludeceonio.h> 1. void maind 2 8. int mark1,mark2,mark3.avE; 4. reer; 5. printi(“Enter marks of 3 subjects (between 0-100)\n"); 6. print"Entar arks of first subject" 7. woanftea", Anwar); 8. _printi*Entor marks of second subj ‘9, “aeanf("%ed", &amark2); 10... printft"Enter marks of third subjes 32, iffmarkl >100 || markt1 18. _print{("Invalid Marks! Please try ax Mod 16. - else ( 16, avge(mark1Fmark2+mark8)9; AT. ilavged0) mark2<0 || mark3>100|| markt) 18. printf Fail"); ww.) 20. else iffavg>=40&&avgc50) { 21. >) printf(Third Diviston’s 22, 23. else iffavg>=508&avE<60) { 24. —__printf("Second Division”); 2.) 26. else iflavg>=60%&ave<5) | 27. printi("First vision"); 28. ’ 29. 30. al. 32, 33, 34. LP. University-{B.Tech LAkash Books else ! , goth 0; ’ rintf"First Division with Distinction”); Souree code of determination of division of a student problem. @ The program graph is given in Figure. i 7 smack, mariah are ver in Figure, The variables used in the prngram are ©-0-0-0-0-0-00-0-0-05 i) The dofine/ use nodes forall variables are given below: ‘S.No. Variable, Definedat node | Used atnode ¥ markt 7 12,16 i mark 8 12,16 a marks u 12,16 4 eve 16 17, 20,28, 28 2017-21LLP. University {B.Tech Akash Books @ 60 15 | 80 | Fintdivision 1 30 40 | 30 | Fal 8. 45 50 | 80 | Thintdivision 8. 55 60 | 50 | Second division w. | 65 zo_|_ 10 | Firstaivision ‘Table 2. Test eases for all definitions 5 Remarks x al 72 p i 9-12 . 5% 1,12 a3 3 16,17 16,26 UNE (Go) AM durpaths, all-uses and all definitions are given below: Q6.(a) List out theroles of Software Quality Asturanceengineer? (4) Paths Definition clear? ‘Ans. Software quality assurance engineer work with software developers ofmprove paient. They run tests on software or applications and ‘All du-paths and all-uses bes ve products. Roles are as follows: Yes Yes Yes Yea Yes Yes : ‘company and governmental guidelines but also reaches the 20,23, 26 ppointed Uy lays can be very costly for All definitions ‘est cass forall du-paths and alluses are given in Table 1 and test cases for all definitions are given in Ta ‘Table 1, Test eases forall paths and all-uses -[ sive. | * mark Expected Output ‘ery high numberof ence | aon iin seid rahi torte aot 2 60 Second division ramp ‘a Soak Test. io - a bad Invalid marks that checks how systems fantion under a beavy namber mar Ls testing ‘a cxain period of tine Inather 4 « Fint division concurrent virtual users performing transactions over er 5 | sa Jnvalid marks‘u-2012 Seventh eae Sra Ting end Gul Aasrice ; sora br pease aged ara af ory, - pee oe a’ ia rotor cae : satpro Ne al wha aretheypesot dcuments a ‘UP Univesity {BTeeh pAkash Books 01-28 vement: A major thrust of TQM is continual poets nt Catal proves es an raat beh analea and et hese recone nde efit meg ‘Total quality uansgerent canbe summarized os a management eysem fg customer-focused organiaton tha iavlesall employes in continual improvenset egy data ad fective communications tointerat the quality dieping into the ature nd avin othe organiration. Many ofthese concepts are preset sndin motivating emplyees at al modern Quality Management Syelems, tha eusesor to TQM, snd timelines, ‘The principle of tola quality management: ‘These elements se cnsdered so crest a TQM that many organizations dtc tes, nef fe asad ils he crpaton operat ‘ero Delectsis based on four key principles: . 1. Quality is simply conformance ruitements aot we wt of measure of ‘performance or 'eodnew Sheperto do the bright the fist tie thane core probes beenrured though prevention, ot pease) 4 ‘The pecormance standard mst be Zero Def, nol"hat gpd ene.Seventh Semester, Software Testing and Quality Assurance soften hidden (inspection, inating defects theso costs are y for the quality improvement 26-2017 Pros: Crosby explains that defects represent. cot waste/ecrap, rework, lost customers, ete). By el sufficiently reduced that the savings more than 0 difficult to achieve; some people ‘attained, They believe it will lead to excessive inspection costs and demoralized staff See ee meinen because ofthe exra stages of increasingly rigorous and expensiveinepection and handling ofthe product, Zero Defects i a dificult el UNIT-AV 8.) What i rogresion testing? Discus varioun catagories of clctivg » ‘must be incorporated in the performed when the functio sion Toning: Corrective regression testing api ou no unmedifed and tat case cane race * ust bedesigned. —~ (3) The Retest-All Strategy: The etestal strategy re ‘may waste time and resources dua toex toa oystom is minor, this strategy woul ‘LP. University-{B.Tech |-Akash Books (4) The Selective Strategy: The selective strate subs cote to reduce therelstng nt. Inthitatgyantunit mat beranen fda ifany ofthe program ett, eg functions ranean The challenge it detily the dependenl 8. (6) Discuss a regression test process for the prioritization of test cases. 65)

You might also like

• Report For Cse 343 Lpu

  

  No ratings yet

  Report For Cse 343 Lpu

  25 pages
• Stqa Py

  

  No ratings yet

  Stqa Py

  69 pages
• Lecture 1 Introduction

  

  No ratings yet

  Lecture 1 Introduction

  31 pages
• Software Testing: ®technical

  

  No ratings yet

  Software Testing: ®technical

  86 pages
• Software Testing 456

  

  No ratings yet

  Software Testing 456

  31 pages
• Eex3467 DS#5

  

  No ratings yet

  Eex3467 DS#5

  50 pages
• Unit 1 Ste

  

  No ratings yet

  Unit 1 Ste

  24 pages
• STM Lab Manual-2021-22

  

  No ratings yet

  STM Lab Manual-2021-22

  66 pages
• Unit 5

  

  No ratings yet

  Unit 5

  18 pages
• Software Testing

  

  No ratings yet

  Software Testing

  20 pages
• It6004-Software Testing Two Marks Question With Answers Unit-I

  

  No ratings yet

  It6004-Software Testing Two Marks Question With Answers Unit-I

  20 pages
• Topic 4 - Software - Testing (SE)

  

  No ratings yet

  Topic 4 - Software - Testing (SE)

  35 pages
• Unit-5 Software Testing

  

  No ratings yet

  Unit-5 Software Testing

  12 pages
• ST Module1

  

  No ratings yet

  ST Module1

  22 pages
• Software Testing Unit-1 PART-1

  

  No ratings yet

  Software Testing Unit-1 PART-1

  56 pages
• Overview of Testing

  

  No ratings yet

  Overview of Testing

  15 pages
• Syllabus

  

  No ratings yet

  Syllabus

  4 pages
• Module - 1

  

  No ratings yet

  Module - 1

  60 pages
• STE qb1 Ans

  

  No ratings yet

  STE qb1 Ans

  8 pages
• Software Testing Polytech 28 Feb 2024

  

  No ratings yet

  Software Testing Polytech 28 Feb 2024

  271 pages
• Software Testing-MSC Level

  

  No ratings yet

  Software Testing-MSC Level

  25 pages
• IAT 2-To Students

  

  No ratings yet

  IAT 2-To Students

  7 pages
• USIT 601 Software Quality Assurance 1 37

  

  No ratings yet

  USIT 601 Software Quality Assurance 1 37

  37 pages
• SQA Unit 1-5

  

  No ratings yet

  SQA Unit 1-5

  323 pages
• Software Quality Assurance: Aamir Khan

  

  No ratings yet

  Software Quality Assurance: Aamir Khan

  29 pages
• Software Testing Unit-1

  

  No ratings yet

  Software Testing Unit-1

  111 pages
• Summary of Lecture 1,6,7

  

  No ratings yet

  Summary of Lecture 1,6,7

  19 pages
• Chapter 4 - Software Testing and Maintenance Overview

  

  No ratings yet

  Chapter 4 - Software Testing and Maintenance Overview

  20 pages
• Chapter1 Testing

  

  No ratings yet

  Chapter1 Testing

  95 pages
• Software Testing 1666362987

  

  No ratings yet

  Software Testing 1666362987

  102 pages
• Unit IV (Testing)

  

  No ratings yet

  Unit IV (Testing)

  106 pages
• STE 1st Unit Important Questions With Answer

  

  No ratings yet

  STE 1st Unit Important Questions With Answer

  11 pages
• Software Testing and Analysis

  

  No ratings yet

  Software Testing and Analysis

  35 pages
• Unit-5 Software Quality Engineering

  

  No ratings yet

  Unit-5 Software Quality Engineering

  9 pages
• Se Unit 4

  

  No ratings yet

  Se Unit 4

  22 pages
• Qat Notes

  

  No ratings yet

  Qat Notes

  33 pages
• Ste W 23

  

  No ratings yet

  Ste W 23

  21 pages
• Software Testing

  

  No ratings yet

  Software Testing

  36 pages
• Unit 4 (KDS-063)

  

  No ratings yet

  Unit 4 (KDS-063)

  20 pages
• Oose Unit-4

  

  100% (1)

  Oose Unit-4

  62 pages
• Oose Unit-4

  

  No ratings yet

  Oose Unit-4

  62 pages
• Oose Unit-4

  

  No ratings yet

  Oose Unit-4

  62 pages
• Unit-1-Basics-Of-Software-Testing-And-Testing-Methods Final With Cover

  

  No ratings yet

  Unit-1-Basics-Of-Software-Testing-And-Testing-Methods Final With Cover

  21 pages
• Software Quality Assurance

  

  No ratings yet

  Software Quality Assurance

  29 pages
• Wollo College of Informatics: University

  

  No ratings yet

  Wollo College of Informatics: University

  38 pages
• Software Testing w1 - Watermark

  

  No ratings yet

  Software Testing w1 - Watermark

  93 pages
• Sof Test

  

  No ratings yet

  Sof Test

  7 pages
• TYCS - Software Testing & Quality Assurance

  

  No ratings yet

  TYCS - Software Testing & Quality Assurance

  96 pages
• Unit 1 ST Rejinpaul

  

  No ratings yet

  Unit 1 ST Rejinpaul

  35 pages
• SE Chapter 7

  

  No ratings yet

  SE Chapter 7

  23 pages
• PAPER: Software Quality Assurance Q2. Write Short Answers To The Following Questions: 1-Explain Black Box Testing and White Box Testing With Example?

  

  No ratings yet

  PAPER: Software Quality Assurance Q2. Write Short Answers To The Following Questions: 1-Explain Black Box Testing and White Box Testing With Example?

  14 pages
• SE Segment-6

  

  No ratings yet

  SE Segment-6

  14 pages
• Unit 4 Se

  

  No ratings yet

  Unit 4 Se

  20 pages
• Chapter 1

  

  No ratings yet

  Chapter 1

  20 pages
• Ste (1st Chapter)

  

  No ratings yet

  Ste (1st Chapter)

  27 pages
• Module 1 - Testing Methodology

  

  No ratings yet

  Module 1 - Testing Methodology

  77 pages
• 2 & 16 Mark Questions and Answers

  

  No ratings yet

  2 & 16 Mark Questions and Answers

  27 pages
• Bcse301l Se Module-5a Smsatapathy

  

  No ratings yet

  Bcse301l Se Module-5a Smsatapathy

  217 pages