0% found this document useful (0 votes)
14 views6 pages

STE

EST answers
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
0% found this document useful (0 votes)
14 views6 pages

STE

EST answers
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF or read online on Scribd
You are on page 1/ 6
Explain criteria to select testing tool. ‘Ans | Criteria for Selecting Test Too! 1M for each factor ‘The Categories for selecting Test Tools are, OR Answer with 1. Meeting requirements; Relevant 2. Technology expectations; Contents 3. Training/skills, 4, Management aspects, 1. Meeting requirements- There are plenty of tools available in the market but rarely do they meet all the requirements of a given product or a given organization. Evaluating different tools for different requirements involve significant effort, money, and time. Given of the plethora of choi available, huge delay is involved in selecting and implementing test tools, 2. Technology expectations- Test tools in general may not allow test developers to extends/modify the functionality of the framework. So extending the functionality requires going back to the tool vendor and involves additional cost and effort. A good number of test tools require their libraries to be linked with product binaries. 3. Training/skills- While test tools require plenty of training, very few vendors. provide the training to the required level. Organization level training is needed to deploy the test tools, as the user of the test suite are not only the test team but also the development team and other areas like configuration management. 4, Management aspects- A test tool increases the system requirement and requires the hardware and software to be upgraded. This increases the cost of the already- expensive test tool. Ti Client-server esting there are several clients communicating with the server. t gh |. Mulipt ser ca aces the sytem a te and hey cam communicate ith theserver Configuration of cient ska to the server wih cert. Cent and server ae connected by rel connection. ‘esting approaches of chen server syste Component Testing: One ne to tine the approsch a est pi for esting ‘tlt snd server ndividally. When server fe fested thes eed of lent ‘imo, wheres testing cheat server sult and Wo fest etwork both "ltrs se Used at ie + Tategrtion testing: Afr sucessful testing of server, tint and network, they te ought gether to orm system esting. + Peformance testing: Sysom performance i std when number of cient communicating wih server a atime. Volume fing and stress testing aye ‘ed for tet, to est under anima oad as well x noc ld expected arin ineratins maybe wed for stress esting. 4+ Concurrency Testing: Is Lery important esting fret server archiete. ‘Waa be posible chat up users may be accessing same record at ie and concureny testing required to understand the Behavior of system ths station, + Disaster Recovery Business continuity testing: When the clos server are communicating wth each ether, there exit poss of Peaking of the ‘nmunication due o various etn or fle Uf ete let or eer or ik am AM Re NIE Tonnasing Wem The raonenr posicatons nant Gasche Oe pose expectations i cas of ony fae ‘esting for extended pers In case of client server applications. generally servers pever shutdown unless teres sane spread Serie Level Agreement (SLA) where server aye shat down for maiteance Ir may be expected Yat server is runing 24X7 for extend perio. One neds 0 conduct testing over fn extended petod o understand Hf service level of uetwork and server ‘serortes ver timed to sre eons ike memory leakage ‘Compadbty Testing: Client server nay be put difetersenvionmenis we the users re-using them in rxtion. Servers may be im iflerent ardware, software, oF operting s9stom envionment than the recommended, ‘Oe esting sucha secuy testing and compliance esting may e avoved rede a5 per testing and ype Ose, toa)6 Le ee! a ee ee” ee, ee, MAHARASHTRA. STATE BOARD OF TECHNICAL EDUCATION (Autos sone “200t Sith Ceres) ‘be done on paper but are ofien tracked i a database 4. Test too and automation are listed and described which are used to test the software, If the team is using automated methods to test software, the tools used, either purchased or writen in-house, must be documented, 5. Metrics, statistics, and! summaries convey the progress being made as the test work Drogresses. They take the form of graphs, charts, and writen reports. Milestones: Milestones are the dates of completion given for various tasks to be performed in testing. These are thoroughly tracked by the test minager and are kept in the documents such as Gantt charts, etc. @_ | What are testdeliverables and milestones? Give any four types of testdeliverables, | 4M “Ans | Test Delverables are the ariiacts which are ghen to the SakehoMers of sofware Tex project during the software development lifecycle, There are diferent test deliverables at | Deliverables every phase of the software development lifecycle. Some test deliverables are provided | a” Milestone before testing phase, some are provided during the testing phase and some after the tre dex testing cycles is over. donde The different types of Test deBverubles are: oM Test cases Documents Test Plan Testing Strategy Test Scripts Test Data Test Traceability. Matrix Test Resuks/reports Test summary report Installconfig. guides Defect Reports. Release notes 1. The test plan describes the overall method to be used to verify thatthe software meets the product specification and the customer's needs. It includes the qualiy objectives, resource needs, schedules, assignments, methods, and so forth 2. "Test cases Ist the specie tems that will be tested an describe the detailed steps that will be followed to verify the software. 3. Bug reports describe the problems found as the test cases are followed. These cou Page dof 3 What is Test Plan? What is its need? List test planning activities. Test Plan: i, Test plan is the project plan for the testing work to be done. ii. It is not a test design specification, a collection of test cases or a set of test procedures; in fact, most of our test plans do not address that level of detail. Need: i, Test Plan Ensures all Functional and Design Requirements are implemented as specified in the documentation. ii. To provide a procedure for Unit and System Testing. iii, To identify the documentation process for Unit and System Testing. iv. To identify the test methods for Unit and System Testing. Activities: 1. Scope Management: Deciding what features to be tested and not to be tested. 2. Deciding Test approach /strategy: Which type of testing shall be done like configuration, integration, localization etc. 3. Setting up criteria for testing: There must be clear entry and exit criteria for different phases of testing. The test strategies for the various features and combinations Page No MAHARASHTRA STATE BOARD OF TECHNICAL EDUCATION (Autonomous) (ISOAEC - 27001 - 2013 Certified) determined how these features and combinations would be tested. 4, Identifying responsibilities, staffing and training needs. 5. Identifying resource requirements. 6. Identifying test deliverables. s Wate & Lime: 12/26/2022 e) State any four limitations of manual testing. Ans slow and costly. 2. It is very labor intensive; it takes a long time to complete tests 3. Manual tests don’t scale well. As the complexity of the software increases the complexity of the testing problem grows exponentially. This leads to an increase in total time devoted to testing as well as total cost of testing. 4, Manual testing is not consistent or repeatable. Variations in how the tests are performed as inevitable, for various reasons. One tester may approach and perform a certain test differently from another, resulting in different results on the same test, because the tests are not being performed identically. 5. Lack of training is the common problem. 6. GUI objects size difference and color combinations are not easy to find in manual testing. 7. Not suitable for large scale projects and time bound projects. 8. Batch testing is not possible, for each test execution Human user interaction is mandatory. 9. Comparing large amounts of data is impractical 10. Processing change requests during software maintenance takes more time. b) | Write important six test cases for the “Login Form” of the Facebook website. ‘Ans Test] Teststep Test dain | Expected | Actual] Status case_ output ‘output no 7 Username filed is Tewill display | Tedisplays | Pass left blank “Enter “Enter Usemame’ | Username" 2 | Enierinvalid user | abe Tt will prompt [It prompt | Pass name “couldn't find | couldn't your account” | find your message account. 3 | Enter validuser | Usemame- [It will display [It displays | Pass name and invalid | abel23—_| ‘Wrong ‘wrong, password Password ~ | password’ password 123, message. message 4 | Enter Valid Usemname- [It wil display Pitdisplays | Pass usemame andno | abcl23—_| ‘Enter “Enter password Password — | password’ password! Pa [MAHARASHTRA STATE HOARD OF TECHNICAL EDUCATION asomec 270013018 Ceri 3] Enver Valid Usemame- | Iwill display | Wdisplays ] Pass username and abel23 | users’ users Password Password ~ | account's accounts €05i22518 | facebook page. | facebook page. © | Clickon Forgowten | - Trwillgoto | It goesto | Pass password?” Find your Find your account page. | account page. ©) _ | Describe defect life cycle with neat diagram, ‘Ans (ame 20/21 i

You might also like