Posts

Showing posts from February, 2013

Importance of Testing in Software Development

Image
Is Testing in Software Development Important? Software testing is a process to determine the quality of the software developed by a developer or programmer. It is a methodological study intended to evaluate the quality-related information of the product. Understanding of the important features and advantages of software testing helps businesses in their day-to-day activities. Rejuvenate the old Software Development using Agile Management & Six sigma In today's cut-throat competition it's very important for every business to perform exceptionally well. Quality is the need of the hour. Software testing basically helps to discover the defect in the software and its configuration. It helps to trace the bugs and errors in your software and recognizing the capacity and the accuracy of the system. Software Testing has many benefits. If the quality of the application is good it can last longer and in perform well in any circumstances like heavy load on your website etc. Thus,

Documentation in Software Testing

Image
Important of Documentation in Software Testing Software testing is an integral part of software development life cycle. With the type of innovative solution expected from software developers, the frequency of bugs appearing in the products developed has also increased. Bugs, as commonly known are the errors in software code that prevent the software to run aptly. It's the work of software tester to apply manual software testing or automated software testing to make software error free. The tester is expected to maintain a cooperative relationship with the software developer and the non-technical (management, clients) as both the parties are involved and necessary for project completion. The software tester has to adopt a tactful and diplomatic approach for issues raised and should have the ability to communicate with both technical and non-technical people in most professional manner.   Software tester is responsible for designing of test plan , test cases, preparing t

Job positions in Software Testing

Image
What are the Job Roles in Software Testing? The End User The simplest method to perform software testing is to run it and monitor its conduct. A lot of evident defects may be easily detected by people with nearly no special knowledge of computer software products and little technical skills. For example usability testing may be conducted with little basic knowledge. Thus, to perform testing of some user-friendly, "plug-and-play" software products, beginner users are usually asked to use the software products. Their behavior and complexities in using are observed and related data is recorded for usability estimation and betterment. In this case, the testing involves the actual beginner users as software testers, but it may also involve skilled testers who observe and record the testing data. If we are talking about automated data recording, the part of the skilled software tester in this case can be eliminated. Professional Testers Well, a lot of people have the

The Fundamentals of Software Testing - Part 2

Image
What is The Fundamentals of Software Testing?  - Part 2 Please refer to part 1 before reading any further! Evaluating exit criteria and reporting:   The test “exit criteria” (established during “Test planning and control”) indicate that testing is complete.  Test closure activities: Ensure that all documentation has been correctly completed  Close down and archive the test environment, infrastructure and testware Hand over testware to maintenance team  Log lessons learned The psychology of testing:   Selecting the appropriate individual(s) to perform the tests, and communicating the results of the tests to the developers, requires a basic understanding of the psychology of testers and developers. The ISEB Software Testing guidance provides a hierarchy of ‘independence’ – that is, a list of individuals who could potentially test the software, gradated according to their perceived level of detachment from the development process : The authors of the co

The Fundamentals of Software Testing - Part 1

Image
What is The Fundamentals of Software Testing? - Part 1   “The Fundamentals of Software Testing ” is the first module of the ISEB Software Testing Foundation course and examination syllabus. ISEB recommend that Software Testing Foundation students spend 20% of their study time on the Software Testing Fundamentals course section. “The Fundamentals of Software Testing” is also the title of the opening chapter in the official ISEB Software Testing manual. Understanding the fundamentals of software testing is clearly crucial to achieving proficiency according to the ISEB software testing professional standards. But what, precisely, are these “fundamentals” of software testing, and what do you need to know in order to pass the ISEB Software Testing Foundation examination? Why is testing necessary? According to Peter Morgan (freelance testing practitioner and member of the ISEB Software Testing Accreditation and Examination panel), an unnecessarily high proportion of IT syst

ISTQB Dumps, Exam Paper 45: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  26 Question: Describe the stages of testing and what the objectives are at each stage.  Answer: Component Testing Lowest level of testing, detail, finding faults, performed by the developers Component Integration Combining components, testing interfaces, performed by developers, various types of integration (top-down, functional, bottom up and big bang). Business scenarios and non-functional aspects if possible. System Testing (functional and non-function) Testing the system as a whole. Testing requirements and business processes. Also testing non-functional aspects such as Performance, usability etc. System Integration Testing the system with other systems and networks Acceptance Testing Testing by users/customers to gain confidence that the system is going to support the business as well as meet their requirements.

ISTQB Dumps, Exam Paper 44: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  25 Question:     Write down any potential problems a fault log may have.   Answer:   Potential issues: No date on log as to when raised No keywords (i.e. screen) so that searches can be performed preventing duplication of fault logs No status of the log (opened/fixed/closed/cleared etc.) No owner of the log. Has priority – but no severity (i.e. risk to the customer) No version number of the system being tested – it is very likely that the testers are on a different version to development and that it was a fault but has been inadvertently fixed on this latest software Query the priority of this log No actual error message on the log – this may give some clue to the developer about the nature of the fault Response seems to be leading to a dialogue – if we are not careful this fault will never be fixed! Tester should talk to the developer rather than sending another message via the fault log. The response by

ISTQB Dumps, Exam Paper 43: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  24 Questions: An ATM has been specified to work in the following way: Enter a card and if the card is invalid reject the card and exit system. If it is a valid card then enter a PIN number. Check to see if the PIN is invalid – if it is then display a message ‘invalid pin number, please re-enter’. If 3 attempts are made with an invalid pin then the machine keeps the card. If it is a valid PIN then the user can select one of the following transactions: • Cash Withdrawal without receipt • Cash Withdrawal with receipt • Balance Enquiry • Statement request • Cancel What tests would you produce to test this application? State any assumptions when testing Answer: 1. Invalid Card – reject card and exit 2. Valid Card and Invalid PIN – error message ‘invalid pin…’ (then enter valid pin) 3. Valid Card and Invalid PIN – error message ‘invalid pin…’ (then enter another 2 invalid Pins) 4. Valid Card, Valid Pin & Cancel (c

ISTQB Dumps, Exam Paper 42: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  23 Question: Scenario: You are testing 2 programs and have 3 weeks to test them both. Having run all of your tests on both programs you finish testing within 2 weeks. You need to decide which of the 2 programs you would re-visit and run further tests against. Choose which program you would re-test (can choose only one!) – and state you reasons: Program A Programmer: A Complexity Level: 2 Lines of Code: 2000 Number of tests: 100 Number of bugs found: 10 (1 high severity, 3 medium & 6 low) Program B Programmer: B Complexity Level: 2 Lines of Code: 2000 Number of tests: 100 Number of bugs found: 50 (10 high severity, 25 medium & 15 low) Answer: Key points: 1. Different programmers wrote A and B 2. Complexity level of the programs are the same 3. Size of the programs are the same 4. Tester is the same for testing A and B 5. Number of tests run on both programs is the same 6. Number of bugs is higher

ISTQB Dumps, Exam Paper 41: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  22 Question: How would you prioritise your tests (list 5)? Answer ask the customer to prioritise the requirements ask the customer to prioritise the tests what is most critical to the customer’s business test where a failure would be most severe test where failures would be most visible test where failures are most likely areas changed most often areas with most problems in the past most complex areas, or technically critical

ISTQB Dumps, Exam Paper 40: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part  21 Question: Describe what you understand about the term “Static Testing” and list 3 static testing techniques Answer: Static Testing is non-execution of the code. Techniques include; reviews, inspections, walkthroughs, individual techniques such as desk checking, data-stepping and proofreading. There is also static analysis (data flow and control flow analysis)

ISTQB Dumps, Exam Paper 39: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 20 Question: A hotel telephone system can perform 3 functions: • Call another hotel room by entering a room number (201 to 500) • Call an external line by entering a 9, followed by the number • Call various hotel services • 0 = Operator • 7 = Room Service • 8 = Reception Write a set of test cases to adequately test this telephone system Answer: Positive/Valid Tests Input Expected Result 0 Operator 201 Room 201 (valid boundary) 405 Room 405 (valid partition) 500 Room 500 (valid boundary) 7 Room Service 8 Reception 9 Outside line Negative/In-valid Tests Input Expected Result 1 Error 6 Error 200 Error (invalid boundary) 501 Error (invalid boundary) 550 Error (invalid partition) Any other button Error Destructive Tests What if I accidentally hit multiple buttons? What if I entered an 0800 number without first getting an outside line (operator should answer)

ISTQB Dumps, Exam Paper 38: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 19 Question Why do you consider testing to be necessary? Answer: There are faults in the software Failures in live operation can be expensive Sometime a ‘legal’ or contractual requirement To asses the quality of the software To preserve the quality of the software To help achieve quality software (by finding and removing the faults)

ISTQB Dumps, Exam Paper 37: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 18 Question: How would you test these requirements: a) The system must be user-friendly b) The system must be easy to install c) The following response times are to be achieved with the new system: • Initial loading of the web application must be achieved within 3 seconds • Updating of the information on the web page must be no more than 5 seconds Answer: a) The system must be user-friendly    Questions to ask: Friendly to whom? Who are the users? Test approaches: Talk to the users Document assumptions Compile test scenarios for people who have not seen the system Document tests and review these with the users     b) The system must be easy to install   Questions to ask:  For whom?  Is there any installation documentation to follow?   Test approaches: Follow installation documentation (if there is any) Allow tests to be run by an inexperienced user to see how easy it is  Documen

ISTQB Dumps, Exam Paper 36: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 17 Question: Name 2 standards that refer to testing Answer: Any of the following: BS 7925-1 (Glossary of testing terms) BS7925-2 (Component Testing) ISO9000 and ISO9001 (Quality standards) IEEE829 (Test Documentation) IEEE1028 (Reviews), IEEE1044 (Incidents)

ISTQB Dumps, Exam Paper 35: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 16     Question:   List 3 test tool categories and describe what each can do.       Answer: Requirement Testing Tools Test Design Tools Test Data Preparation Tools Regression Testing tools Debug Tools Dynamic Analysis Tools Coverage Measurement Tools Static Analysis Tools Performance Testing Tools Test Management Tools Network monitoring tools Test Harness or Simulation tools The importance of this question is to see if the candidate has any knowledge about tools. We do not want the names of tools but want to know if the candidate can distinguish between the types of tool.    

ISTQB Dumps, Exam Paper 34: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 15 Question Do you consider testing tools to be valuable during the testing process – why/why not? Answer: Testing tools are very important to assist the tester in their work. Using tools can also potentially make the tester more efficient in their work – they are able to run more tests (using regression testing for example). Or they can quickly compare 3 reports (comparison tool). The tools in themselves however do not make good testers and also should not be considered if the test process is in ‘chaos’.

ISTQB Dumps, Exam Paper 33: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 14 Question: Scenario: You have planned to run 600 tests on your own. Each test will take approximately 10 minutes to run. Your manager has told you that you must complete these tests within one week. What would you do? Answer: Assuming there are 7 hours per working day. This task would take you: 600x10 = 6000 minutes = 100 hours = 14.286 days There are a number of options that could be considered: Work overtime (this should not be considered as a first resort) Ask for more staff to help (again this may not be the best approach, particularly if you need to spend time training and mentoring the new staff) WE SHOULD: Re-prioritise our tests and run the most important tests first Assuming that not all the 600 tests would have been run within this time, risk assessment need to be made as to the consequences of not running the extra tests. After this initial week and the system is implemented there is no reason why

ISTQB Dumps, Exam Paper 32: ISEB ISTQB Foundation Software Testing

Image
ISTQB Question Dumps For Software Testing -  Part 13 Question: Explain what you understand by the terms Regression Testing and Re-Testing Answer: Regression Testing: Running tests to ensure that the software has not regressed in anyway as a result of changes to the software and/or environment. Regression testing is running passed tests again to ensure that they still pass. Re-Testing: This is running a test again that had found a fault to check that the fault has been fixed correctly. Re-testing is running a failed test again to ensure that it now passes.