Basics about Manual Testing & Interview Questions

<div dir="ltr" style="text-align: left;" trbidi="on"><div style="vertical-align: top;"><br />Here We are Providing Information about what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics. <b></b><br /><b><br /></b><b><span style="font-size: large;"><span style="color: red;">Manual Testing Basics & Interview Questions</span></span></b><br /><br /><br /><b>1 . What is diff. between CMMI and CMM levels?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">Ans:  CMM: - this is applicable only for software industry. KPAs -18</div><div style="vertical-align: top;">CMMI: - This is applicable for software, out sourcing and all other industries. KPA - 25</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>2. What is the scalability testing?<o:p></o:p></b></div><div style="vertical-align: top;"><b>Ans :</b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">1. Scalability is nothing but how many users that the application should handle<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">2. Scalability is nothing but maximum no of users that the system can handle</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Scalability testing is a subtype of performance test where performance requirements for response time, throughput, and/or utilization are tested as load on the SUT is increased over time.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. As a part of scalability testing we test the expandability of the application. In scalability we test 1.Applicaation scalability, 2.Performance scalability</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Application scalability: to test the possibility of implementing new features in the system or updating the existing features of the system. With the help of design doc we do this testing</div><div style="vertical-align: top;">Performance scalability: To test how the s/w perform when it is subjected to varying loads to measure and to evaluate the</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Performance behavior and the ability for the s/w to continue to function properly under different workloads.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">–> To check the comfort level of an application in terms of user load. And user experience and system tolerance levels</div><div style="vertical-align: top;">–> The point within an application that when subjected to increasing workload begin to degrade in terms of end user experience and system tolerance</div><div style="vertical-align: top;">–> Response time</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Execution time</div><div style="vertical-align: top;">System resource utilization</div><div style="vertical-align: top;">Network delays</div><div style="vertical-align: top;"> stress testing<span style="font-family: Symbol; mso-ascii-font-family: "Times New Roman"; mso-char-type: symbol; mso-hansi-font-family: "Times New Roman"; mso-symbol-font-family: Symbol;">è</span></div><div style="vertical-align: top;"><span style="font-family: Symbol; mso-ascii-font-family: "Times New Roman"; mso-char-type: symbol; mso-hansi-font-family: "Times New Roman"; mso-symbol-font-family: Symbol;"><br /></span></div><div style="vertical-align: top;"><b>3. What is status of defect when you are performing regression testing?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans:</b> Fixed Status</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>4. What is the first test in software testing process?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">A) Monkey testing</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">B) Unit Testing</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">c) Static analysis</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">d) None of the above</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Ans:</b>  Unit testing is the first test in testing process, though it is done by developers after the completion of </div><div style="vertical-align: top;">coding it is correct one.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>5. When will the testing starts? a) Once the requirements are Complete b) In requirement phase?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;"><b>Ans:-</b> Once the requirements are complete.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;"><br /></span></div><div style="vertical-align: top;">This is Static testing. Here, u r supposed to read the documents (requirements) and it is quite a common issue in S/w industry that many requirements contradict with other requirements. These are also can be reported as bugs. However, they will be reviewed before reporting them as bugs (defects).</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>6. What is the part of Qa and QC in refinement v model?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">Ans: V model is a kind of SDLC. QC (Quality Control) team tests the developed product for quality. It deals only with product, both in static and dynamic testing. QA (Quality Assurance) team works on the process and manages for better quality in the process. It deals with (reviews) everything right from collecting requirements to delivery.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>7. What are the bugs we cannot find in black box?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">Ans:  If there r any bugs in security settings of the pages or any other internal mistake made in coding cannot be found in black box testing.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>8. What are Microsoft 6 rules?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">Ans: As far as my knowledge these rules are used at user Interface test.<o:p></o:p></span></div><div style="vertical-align: top;">These are also called Microsoft windows standards. They are</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>. GUI objects are aligned in windows<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>• All defined text is visible on a GUI object</b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>• </b>Labels on GUI objects are capitalized</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Each label includes an underlined letter (mnemonics)</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Each window includes an OK button, a Cancel button, and a System menu</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>9. What are the steps to test any software through automation tools?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">Ans: First, you need to segregate the test cases that can be automated. Then, prepare test data as per the requirements of those test cases. Write reusable functions which are used frequently in those test cases. Now, prepare the test scripts using those reusable functions and by applying loops and conditions where ever necessary. However, Automation framework that is followed in the organization </span>should strictly follow throughout the process.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>10. What is Defect removable efficiency?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>The DRE is the percentage of defects that have been removed<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">During an activity, computed with the equation below. The DRE can also be computed for each software development activity and plotted on a bar graph to show the relative defect removal efficiencies for each activity. Or, the DRE may be computed for a specific task or technique (e.g. design inspection, code walkthrough, unit test, 6 month operation, etc.) Number Defects Removed</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">DRE = –—————————————————— * 100</div><div style="vertical-align: top;">Number Defects at Start of Process</div><div style="vertical-align: top;">DRE=A/A+B = 0.8</div><div style="vertical-align: top;">A = Testing Team (Defects by testing team)</div><div style="vertical-align: top;">B = customer ( ” ” customer )</div><div style="vertical-align: top;">If dre <=0.8 then good product otherwise not.</div><div style="vertical-align: top;">Qn. Example for bug not reproducible?</div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">A: — Difference in environment.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>11. Difference between adhoc testing and error guessing?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans:</b> Adhoc testing: without test data r any documents performing testing.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Error Guessing</b>: This is a Test data selection technique. The selection criterion is to pick values that seem likely to cause errors.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>12. Diff between test plan and test strategy?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>Test plan: After completion of SRS learning and business requirement gathering test management concentrate on test planning, this is done by Test lead, or Project lead.</span>Test Strategy: Depends on corresponding testing policy quality analyst finalizes test Responsibility Matrix. This is dont by QA. But both  Documents.</div><div class="MsoNormal" style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>13. What is “V-n-V” Model? Why is it called as “V”& why not “U”? Also tell at what Stage Testing should be best to stared?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans:</b>It is called V coz it looks like V. the detailed V model is shown below.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">SRS                          Acceptance testing</div><div style="vertical-align: top;">     \                         /</div><div style="vertical-align: top;">      \                       /</div><div style="vertical-align: top;">    HLD (High Level Design)   System testing</div><div style="vertical-align: top;">       \                    /</div><div style="vertical-align: top;">        \                  /</div><div style="vertical-align: top;">       LLD (Low level      Integration testing</div><div style="vertical-align: top;">             Design)     /</div><div style="vertical-align: top;">          \              /    </div><div style="vertical-align: top;">           \            Unit Testing</div><div style="vertical-align: top;">            \          /</div><div style="vertical-align: top;">             \        /</div><div style="vertical-align: top;">               Coding</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">There is no such stage for which you wait to start testing.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Testing starts as soon as SRS document is ready. You can raise defects that are present in the document. It’s called verification.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>14. What is difference in between Operating System 2000 and OS XP?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>Windows 2000 and Windows XP are essentially the same operating system (known internally as Windows NT 5.0 and Windows NT 5.1, respectively.) Here are some considerations if you’re trying to decide which version to use:<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;"><b>Windows 2000 benefits:<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">1) Windows 2000 has lower system requirements, and has a simpler interface (no “Styles” to mess with).</div><div style="vertical-align: top;">2) Windows 2000 is slightly less expensive, and has no product activation.</div><div style="vertical-align: top;">3) Windows 2000 has been out for a while, and most of the common problems and security holes have been uncovered and fixed.</div><div style="vertical-align: top;">4) Third-party software and hardware products that aren’t yet XP-compatible may be compatible with Windows 2000; check the manufacturers of your devices and applications for XP support before you upgrade.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Windows XP benefits:<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">1) Windows XP is somewhat faster than Windows 2000, assuming you have a fast processor and tons of memory (although it will run fine with a 300 MHz Pentium II and 128MB of RAM).</div><div style="vertical-align: top;">2) The new Windows XP interface is more cheerful and colorful than earlier versions, although the less- cartoon “Classic” interface can still be used if desired.</div><div style="vertical-align: top;">3 Windows XP has more bells and whistles, such as the Windows Movie Maker, built-in CD writer support, the Internet Connection Firewall, and Remote Desktop Connection.</div><div style="vertical-align: top;">4) Windows XP has better support for games and comes with more games than Windows 2000.</div><div style="vertical-align: top;">5) Manufacturers of existing hardware and software products are more likely to add Windows XP compatibility now than Windows 2000 compatibility.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>15. What is bug life cycle?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>New: when tester reports a defect<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">Open: when developer accepts that it is a bug or if the developer rejects the defect, then the status is turned into “Rejected”</div><div style="vertical-align: top;">Fixed: when developer make changes to the code to rectify the bug…</div><div style="vertical-align: top;">Closed/Reopen: when tester tests it again. If the expected result shown up, it is turned into “Closed” and if the problem resists again, it’s “Reopen</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>16. What is deferred status in defect life cycle?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans: </b>Deferred status means the developer accepted the bus, but it is scheduled to rectify in the next build</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>17. What is smoke test?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans: </b>Testing the application whether it’s performing its basic functionality properly or not, so that the test team can go ahead with the application</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>18. Do you use any automation tool for smoke testing?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans:-</b> Definitely can use.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>20. What is Verification and validation?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans:</b> Verification is static. No code is executed. Say, analysis of requirements etc. Validation is dynamic. Code is executed with scenarios present in test cases.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>21. What is test plan and explain its contents?<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Ans:</b> Test plan is a document which contains the scope for testing the application and what to be tested, when to be tested and who to test.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>22. Advantages of automation over manual testing?</b><br /></div><div style="vertical-align: top;"><b>Ans :</b> Time, resource and Money<br /></div><div style="vertical-align: top;"><b>23. What is ADhoc testing?</b><br /></div><div style="vertical-align: top;"><b>Ans :</b> AdHoc means doing something which is not planned.<br /></div><div style="vertical-align: top;"><b>24. What is mean by release notes?</b><br /></div><div style="vertical-align: top;"><b>Ans:</b> It’s a document released along with the product which explains about the product. It also contains about the bugs that are in deferred status.<br /></div><div style="vertical-align: top;"><b>25. Scalability testing comes under in which tool?</b><br /></div><div style="vertical-align: top;"><b>Ans:</b> Scalability testing comes under performance testing. Load testing, scalability testing both are same.<br /></div><div style="vertical-align: top;"><b>26. What is the difference between Bug and Defect?</b><br /></div><div style="vertical-align: top;"><b>Ans:</b> Bug: Deviation from the expected result. Defect: Problem in algorithm leads to failure.</div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">A Mistake in code is called Error.</span><br /><br /><span style="font-family: "Times New Roman","serif";"><o:p></o:p></span></div><div style="vertical-align: top;">Due to Error in coding, test engineers are getting mismatches in application is called defect.</div><div style="vertical-align: top;">If defect accepted by development team to solve is called Bug.<br /><br /></div><div style="vertical-align: top;"><b>27. What is hot fix?</b><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>A hot fix is a single, cumulative package that includes one or more files that are used to address a problem in a software product. Typically, hot fixes are made to address a specific customer situation and may not be distributed outside the customer organization.<o:p></o:p></span></div><div style="vertical-align: top;">Bug found at the customer place which has high priority.<br /></div><div style="vertical-align: top;"><b>28. What is the difference between functional test cases and comparability test cases?</b><br /></div><div style="vertical-align: top;"><b>Ans: </b>There are no Test Cases for Compatibility Testing; in Compatibility Testing we are Testing an application in different Hardware and software. If it is wrong plz let me know.<br /></div><div style="vertical-align: top;"><b>29. What is Acid Testing?</b><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans:</b> ACID Means:<o:p></o:p></span></div><div style="vertical-align: top;">ACID testing is related to testing a transaction.</div><div style="vertical-align: top;">A-Atomicity</div><div style="vertical-align: top;">C-Consistent</div><div style="vertical-align: top;">I-Isolation</div><div style="vertical-align: top;">D-Durable</div><div style="vertical-align: top;">Mostly this will be done database testing.<br /></div><div style="vertical-align: top;"><b>30. What is the main use of preparing a traceability matrix?</b><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><b>Ans: </b>To Cross verify the prepared test cases and test scripts with user requirements.<o:p></o:p></span></div><div style="vertical-align: top;">To monitor the changes, enhance occurred during the development of the project.</div><br /><div style="vertical-align: top;">Traceability matrix is prepared in order to cross check the test cases designed against each requirement, hence giving an opportunity to verify that all the requirements are covered in testing the application.<br /><br /><br /><br /><br />what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics </div></div>

Basics about Manual Testing & Interview Questions

Here We are Providing Information about what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Te...

Read more »

Software Testing Basics and Basic Interview Questions

<div dir="ltr" style="text-align: left;" trbidi="on"><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Here we are providing what is Software Testing, Software Testing Basics, Software Testing Interview Questions and Software Testing Tutorials. Here in this page we are explaining about what is Soft Ware, Product and Project. And also Along with What is Deference between Project and Product, Why Testing is Necessary Information.<b><o:p></o:p></b></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">What is Software Testing?<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Testing is the Process of Verifying or we developing Right Product or Not and also Validating does the Developed product is right or Not. Verification and Validation is Called Software Testing.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><b>Software Testing = Verification (WBT)+Validation(BBT)</b><o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: Times New Roman, serif;">Testing is the Process, Where Tester intention is find out number of Defects, Uncovered Functionality as uncovered errors in a Given Software.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: Times New Roman, serif;"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Testing will be done after getting initial Build from Developer, Before Releasing a Product in to Production.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Why Testing is Necessary? <o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";"><span style="color: blue;">Required: </span><o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";">* </span></b><span style="font-family: "Times New Roman","serif";">Because software is Likely to Have Faults.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">* To Learn About the reliability of the Software.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">* Because failures can be very expensive.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">* To avoid being “Misused” by Customers.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">* To Stay in Business.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="font-family: 'Times New Roman', serif;"><span style="color: blue;">Not Required:</span><span style="color: red;"><o:p></o:p></span></span></b></div><div class="MsoNormal"><b><span style="font-family: 'Times New Roman', serif;"><span style="color: blue;"><br /></span></span></b></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         * </span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";">To fill the time between Delivery of the Software and the release date.<b><o:p></o:p></b></span></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoListParagraphCxSpLast" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         * </span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";">Because Testing is included in the Project Plane.<b><o:p></o:p></b></span></div><div class="MsoListParagraphCxSpLast" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Software:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">A set of Programs and Minimal Data to Run a System is called Software.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Software Types:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         </span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";">Accounting Software.<o:p></o:p></span></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoListParagraphCxSpMiddle" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         </span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";">Email Software.<o:p></o:p></span></div><div class="MsoListParagraphCxSpMiddle" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoListParagraphCxSpLast" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         </span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";">Mobile and etc.<o:p></o:p></span></div><div class="MsoListParagraphCxSpLast" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Product:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Developing software for Multiple Customers developing upon Current Market Technology is Called Product.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";">Example:</span></b><span style="font-family: "Times New Roman","serif";">  Mobiles, MS Office, MS Windows etc.<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Project or Application:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Developing a Software for Specific Customer developing upon own Business Requirement is Called Project<b>.<o:p></o:p></b></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><b><br /></b></span></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";">Example:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Health care<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Software Testing Types:<o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";">Mainly Software Testing is Two Types, There are<o:p></o:p></span></div><div class="MsoNormal"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">      <b>   </b></span></span><!--[endif]--><span style="font-family: "Times New Roman","serif";"><b>Manual Testing<o:p></o:p></b></span></div><div class="MsoListParagraphCxSpFirst" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><span style="font-family: "Times New Roman","serif";"><b><br /></b></span></div><div class="MsoListParagraphCxSpMiddle" style="mso-list: l0 level1 lfo1; text-indent: -.25in;"><!--[if !supportLists]--><b><span style="font-family: Symbol; mso-bidi-font-family: Symbol; mso-fareast-font-family: Symbol;">·<span style="font-family: 'Times New Roman'; font-size: 7pt;">         </span></span><!--[endif]--></b><span style="font-family: "Times New Roman","serif";"><b>Automation Testing</b><o:p></o:p></span></div><div class="MsoListParagraphCxSpLast"><br /></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif"; font-size: 16.0pt; line-height: 115%;"><span style="color: #20124d;">Software Testing Interview Questions</span><o:p></o:p></span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif"; font-size: 16.0pt; line-height: 115%;"><br /></span></b></div><div class="MsoNormal"><b><span style="color: red; font-family: "Times New Roman","serif";">Manual Testing Basics and Manual Testing Interview Questions:</span></b></div><div class="MsoNormal"><b><span style="font-family: "Times New Roman","serif";"><br /></span></b></div><div style="vertical-align: top;"><span class="apple-style-span"><b>Explanation of some common software testing terms?</b></span></div><div style="vertical-align: top;"><span class="apple-style-span"><b><br /></b></span></div><div style="vertical-align: top;">Testing objectives include</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">1. Testing is a process of executing a program with the intent of finding an error.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">2. A good test case is one that has a high probability of finding an as yet undiscovered error.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. A successful test is one that uncovers an as yet undiscovered error.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Testing should systematically uncover different classes of errors in a minimum amount of time and with a minimum amount of effort. A secondary benefit of testing is that it demonstrates that the software appears to be working as stated in the specifications. The data collected through testing can also provide an indication of the software’s reliability and quality. But, testing cannot show the absence of defect — it can only show that software defects are present.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">White Box Testing<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">White box testing is a test case design method that uses the control structure of the procedural design to derive test cases. Test cases can be derived that<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">1. Guarantee that all independent paths within a module have been exercised at least once,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Exercise all logical decisions on their true and false sides,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Execute all loops at their boundaries and within their operational bounds, and</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Exercise internal data structures to ensure their validity.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">The Nature of Software Defects</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">Logic errors and incorrect assumptions are inversely proportional to the probability that a program path will be executed. General processing tends to be well understood while special case processing tends to be prone to errors.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">We often believe that a logical path is not likely to be executed when it may be executed on a regular basis. Our unconscious assumptions about control flow and data lead to design errors that can only be detected by path testing.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Typographical errors are random.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Basis Path Testing<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">This method enables the designer to derive a logical complexity measure of a procedural design and use it as a guide for defining a basis set of execution paths. Test cases that exercise the basis set are guaranteed to execute every statement in the program at least once during testing.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Flow Graphs<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">Flow graphs can be used to represent control flow in a program and can help in the derivation of the basis set. Each flow graph node represents one or more procedural statements. The edges between nodes represent flow of control. An edge must terminate at a node, even if the node does not represent any useful procedural statements. A region in a flow graph is an area bounded by edges and nodes. Each node that contains a condition is called a predicate node. Cyclomatic complexity is a metric that provides a quantitative measure of the logical complexity of a program. It defines the number of independent paths in the basis set and thus provides an upper bound for the number of tests that must be performed.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">The Basis Set<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">An independent path is any path through a program that introduces at least one new set of processing statements (must move along at least one new edge in the path). The basis set is not unique. Any number of different basis sets can be derived for a given procedural design. Cyclomatic complexity, V(G), for a flow graph G is equal to<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">1. The number of regions in the flow graph.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. V(G) = E - N + 2 where E is the number of edges and N is the number of nodes.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. V(G) = P + 1 where P is the number of predicate nodes.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Deriving Test Cases</b></div><div style="vertical-align: top;"><b><br /></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">1. From the design or source code, derive a flow graph.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">2. Determine the cyclomatic complexity of this flow graph.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Even without a flow graph, V(G) can be determined by counting the number of conditional statements in the code.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Determine a basis set of linearly independent paths.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">5. Predicate nodes are useful for determining the necessary paths.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">6. Prepare test cases that will force execution of each path in the basis set.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">7. Each test case is executed and compared to the expected results.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Automating Basis Set Derivation<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">The derivation of the flow graph and the set of basis paths is amenable to automation. A software tool to do this can be developed using a data structure called a graph matrix. A graph matrix is a square matrix whose size is equivalent to the number of nodes in the flow graph. Each row and column correspond to a particular node and the matrix corresponds to the connections (edges) between nodes. By adding a link weight to each matrix entry, more information about the control flow can be captured. In its simplest form, the link weight is 1 if an edge exists and 0 if it does not. But other types of link weights can be represented:<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">• The probability that an edge will be executed,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• The processing time expended during link traversal,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• The memory required during link traversal, or</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• The resources required during link traversal.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Graph theory algorithms can be applied to these graph matrices to help in the analysis necessary to produce the basis set.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Loop Testing<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">This white box technique focuses exclusively on the validity of loop constructs. Four different classes of loops can be defined:<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">1. Simple loops,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Nested loops,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Concatenated loops, and</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Unstructured loops.</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif";">Simple Loops<o:p></o:p></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div style="vertical-align: top;">The following tests should be applied to simple loops where n is the maximum number of allowable passes through the loop:</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">1. Skip the loop entirely,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Only pass once through the loop,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. M passes through the loop where m < n,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. n - 1, n, n + 1 passes through the loop.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Nested Loops<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">The testing of nested loops cannot simply extend the technique of simple loops since this would result in a geometrically increasing number of test cases. One approach for nested loops:</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">1. Start at the innermost loop. Set all other loops to minimum values.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Conduct simple loop tests for the innermost loop while holding the outer loops at their minimums. Add tests for out-of-range or excluded values.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Work outward, conducting tests for the next loop while keeping all other outer loops at minimums and other nested loops to typical values.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Continue until all loops have been tested.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Concatenated Loops<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">Concatenated loops can be tested as simple loops if each loop is independent of the others. If they are not independent (e.g. the loop counter for one is the loop counter for the other), then the nested approach can be used.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Unstructured Loops<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">This type of loop should be redesigned not tested!!!</div><div style="vertical-align: top;">Other White Box Techniques</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">Other white box testing techniques include</span></b><span style="font-family: "Times New Roman","serif";">:<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">1. Condition testing</div><div style="vertical-align: top;"> Exercises the logical conditions in a program.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Data flow testing</div><div style="vertical-align: top;"> Selects test paths according to the locations of definitions and uses of variables in the program.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Black Box Testing<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">Introduction<o:p></o:p></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;"><br /></span></b></div><div style="vertical-align: top;">Black box testing attempts to derive sets of inputs that will fully exercise all the functional requirements of a system. It is not an alternative to white box testing. This type of testing attempts to find errors in the following categories:</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">1. Incorrect or missing functions,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. Interface errors,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Errors in data structures or external database access,</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Performance errors, and</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">5. Initialization and termination errors.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">Tests are designed to answer the following questions:</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">1. How is the function’s validity tested?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. What classes of input will make good test cases?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Is the system particularly sensitive to certain input values?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. How are the boundaries of a data class isolated?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">5. What data rates and data volume can the system tolerate?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">6. What effect will specific combinations of data have on system operation?</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">White box testing should be performed early in the testing process, while black box testing tends to be applied during later stages. Test cases should be derived which</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">1. Reduce the number of additional test cases that must be designed to achieve reasonable testing, and<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;"><br /></span></div><div style="vertical-align: top;">2. Tell us something about the presence or absence of classes of errors, rather than an error associated only with the specific test at hand.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Equivalence Partitioning<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">This method divides the input domain of a program into classes of data from which test cases can be derived. Equivalence partitioning strives to define a test case that uncovers classes of errors and thereby reduces the number of test cases needed. It is based on an evaluation of equivalence classes for an input condition. An equivalence class represents a set of valid or invalid states for input conditions.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Equivalence classes may be defined according to the following guidelines:<o:p></o:p></b></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;">1. If an input condition specifies a range, one valid and two invalid equivalence classes are defined.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. If an input condition requires a specific value, then one valid and two invalid equivalence classes are defined.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. If an input condition specifies a member of a set, then one valid and one invalid equivalence class are defined.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. If an input condition is Boolean, then one valid and one invalid equivalence class are defined.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Boundary Value Analysis<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";">This method leads to a selection of test cases that exercise boundary values. It complements equivalence partitioning since it selects test cases at the edges of a class. Rather than focusing on input conditions solely, BVA derives test cases from the output domain also. BVA guidelines include:<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;">1. For input ranges bounded by a and b, test cases should include values a and b and just above and just below a and b respectively.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. If an input condition specifies a number of values, test cases should be developed to exercise the minimum and maximum numbers and values just above and below these limits.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. Apply guidelines 1 and 2 to the output.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. If internal data structures have prescribed boundaries, a test case should be designed to exercise the data structure at its boundary.</div><div style="vertical-align: top;"><b><span style="color: red;">Cause-Effect Graphing Techniques<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">Cause-effect graphing is a technique that provides a concise representation of logical conditions and corresponding actions. There are four steps:<o:p></o:p></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;"><br /></span></b></div><div style="vertical-align: top;">1. Causes (input conditions) and effects (actions) are listed for a module and an identifier is assigned to each.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">2. A cause-effect graph is developed.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">3. The graph is converted to a decision table.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">4. Decision table rules are converted to test cases.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b>Qn. Explain the Manual testing process?</b></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Manual Testing Process:<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">Process is a roadmap to develop the project is consists a number of sequential steps</span></b><span style="font-family: "Times New Roman","serif";">.<o:p></o:p></span></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif";"><br /></span></div><div style="vertical-align: top;"><b><span style="color: red;">Software Testing Life Cycle:<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">• Test Plan</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Test Development</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Test Execution</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Analyze Results</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Defect Tracking</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Summaries Report</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Test Plan:<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div class="MsoNormal" style="vertical-align: top;"><span style="font-family: "Times New Roman","serif"; font-size: 12.0pt; line-height: 115%;">It is a document which describes the testing environment, purpose, scope, objectives, test strategy, schedules, mile stones, testing tool, roles and responsibilities, risks, training, staffing and who is going to test the application, what type of tests should be performed and how it will track the defects.<o:p></o:p></span></div><div style="vertical-align: top;"><b><br /></b></div><div style="vertical-align: top;"><b>Test Development:</b></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Preparing test cases</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Preparing test data</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Preparing test procedure</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Preparing test scenario</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Writing test script</div><div style="vertical-align: top;"><br /></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif";">Test Execution:<o:p></o:p></span></b></div><div class="MsoNormal" style="vertical-align: top;"><b><span style="color: red; font-family: "Times New Roman","serif";"><br /></span></b></div><div style="vertical-align: top;">In this phase we execute the documents those are prepared in test development phase.</div><div style="vertical-align: top;">Analyze result:</div><div style="vertical-align: top;">Once executed documents will get results either pass or fail. we need to analyse the results during this phase.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Defect Tracking:<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">Whenever we get defect on the application we need to prepare the bug report file and forwards to Test Team Lead and Dev Team. The Dev Team will fix the bug. Again we have to test the application. This cycle repeats till we get the software with our defects.</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><b><span style="color: red;">Summaries Reports:<o:p></o:p></span></b></div><div style="vertical-align: top;"><b><span style="color: red;"><br /></span></b></div><div style="vertical-align: top;">• Test Reports</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">• Bug Reports</div><div style="vertical-align: top;"><br /></div><br /><div style="vertical-align: top;">• Test Documentation</div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;"><br /></div><div style="vertical-align: top;">what is Software Testing, Software Testing Basics, Software Testing Interview Questions, Software Testing Tutorials, Software, Product, Project,What is Deference between Project and Product, Why Testing is Necessary Information, Manual Testing Interview Questions, Manual Testing Tutorials, Basics about Manual Testing, Manual Testing Basics</div></div>

Software Testing Basics and Basic Interview Questions

Here we are providing what is Software Testing, Software Testing Basics, Software Testing Interview Questions and Software Testing Tutorials...

Read more »