Skip to main content

Posts

Showing posts with the label ISEB

Business Analysis and Quality Assurance Uncovered!

Business Analysis and Quality Assurance Uncovered! Business Analysis and Quality Assurance have one goal in common to support overall strategic goals of Business. Business Analyst does so by making information refined and processed after information gathering and analysis. Quality Assurance takes on the mission from this point and prepares various artefact that help in Assuring Quality and conformance to requirement at every stage of the testing process. Software Testing Training has an extensive coverage for both. These both need a crystal clear understanding of the Business Domain. At every stage the domain must be considered as Nucleus where all the activities must direct towards. Any deviation from the centrally focused domain can be the cause of rework and change requests. That consumes both time and attention. These both roles can be well juggled via Software Testing Training. When there is a thorough understanding of domain a Quality Assurance personal can devise the best ...

Software Testing Methodologies: Black Box, White Box, Waterfall, V-Model, Spiral Model Explained!

Software Testing Methodologies: Black Box, White Box, Waterfall, V-Model, Spiral Model Explained! Introduction Software development includes different kinds of testing methods. Software testing is an important part of software development. Writing a piece of code is very important, but testing the code is much more important than writing it. Software testing means that testing the code using different conditions and to check the quality of output and whether the output is as expected or not. Before testing the code, the developer will prepare a set of test cases with varying conditions to check the output. Any errors, bugs or difference in result can be found out during the testing phase. It is the job of software quality assurance engineer to conduct the testing and check the results. Though you have many software testing methodologies available, the below listed are the most frequently used by the software engineers . Black box It is the commonly used testing met...

What is Agile Software Testing?

What is Agile Software Testing? History To understand the testing process in Agile development methodology, it is important to understand the paradigm of Agile development. The Agile Development paradigm is not new. Although Agile Software Development Manifesto was launched in February 2001, the concepts existed well before this and have been expressed in different ways. Development methodology spiral is an example.   What is Agile Software Development?  The Agile Software Development focuses mainly on an iterative development and delivery. Developers and end users to communicate closely, and the software is built. A working software is delivered in a short period of time and based on the comments more features and capabilities are added. The emphasis is on customer satisfaction by providing software quickly with minimal features and improvisation based on the feedback. The client is closely involved in software design and development process. Delivery tim...

Contract Test Analyst - ISEB / ISTQB - Job £350p/d - £380p/d

Contract Test Analyst - London - 6 months - £350p/d - £380p/d - Payments - Quality Centre - QTP - ISEB Our client is one of the healthiest banks in the world at this current time (virtually zero exposure to the sub-prime market). Furthermore, if you like the excitement of working in the IT banking sector, but don't especially enjoy the culture of long hours and intense pressure this could be the organisation for you. This organisation respects work / life balance of its employees. A contract opportunity has arisen to join this banking group as Test Analyst to concentrate of their payments systems. Job purpose: Main Requirements: Test Planning/Scripting/Data preparation/Execution. Experience with integration testing of payments flows, not just 'user-driven applications'. Whilst the user interface aspect is indeed important, testing the flows of the backend systems including databases and middleware and integration/interfaces between subsystems is key. ...

Senior Test Analyst / QA Engineer (ISEB / ISTQB, Agile) - Job

Senior Test Analyst / QA Engineer (ISEB / ISTQB, Agile) About the Job We are looking for a Senior QA Engineer / Test Analyst with experience of designing, developing and executing test plans in an Agile environment for a market leader and expanding software solutions company in Bedford, Bedfordshire. Any experience of Jira, Wiki and/or Zephyr would be ideal but not essential. As the successful Senior Test Analyst / QA Engineer you will be responsible for designing, developing and executing test plans as well as providing team and technical leadership across an Agile environment involving solution design, test planning, functional testing, defect management and process improvements. As a Senior QA Engineer / Test Analyst you are likely to understand client server and web based applications as well as exposure to tools such as Jira, Wiki and/or Zephyr. A fantastic opportunity to have an influence over future direction of testing activity and the approaches taken. Skil...

ISTQB Exam Question Paper, Part 6

ISTQB Exam Question Paper, Part 6 21 Which of the following should NOT normally be an objective for a test? a) To find faults in the software. b) To assess whether the software is ready for release. c) To demonstrate that the software doesn’t work. d) To prove that the software is correct. 22 Which of the following is a form of functional testing? a) Boundary value analysis b) Usability testing c) Performance testing d) Security testing 23 Which of the following would NOT normally form part of a test plan? a) Features to be tested b) Incident reports c) Risks d) Schedule 24 Which of these activities provides the biggest potential cost saving from the use of CAST? a) Test management b) Test design c) Test execution d) Test planning 25 Which of the following is NOT a white box technique? a) Statement testing b) Path testing c) Data flow testing d) State transition testing 26 Data flow analysis studies: a) possible communications bottlenecks in a prog...

What is Manual Testing?

What is Manual Testing? Manual QA Testing is carried out to identify defects in the test software pertaining to usability testing along with GUI testing area. It proves to be a highly effective form of IT testing since it detects a certain class of bugs successfully, which cannot be detected using test automation technique Now the question arises when to use manual QA testing? Well, the answer to this question redirects us to certain instances listed below. Let us take the case of installations and setups where loading of CD-ROMs and tapes is done by the tester. Also, it's needed in the instance of localization wherein the tester screens & decides if the translation is making some sense or not, whether it's appropriate or not etc. Manual QA testing is also required in the case of error handling and recovery in which the tester needs to be involved in test execution thus highlighting again on the significance of manual testing. Besides the cases listed above, man...

Automation Tools for Regression Testing

Automation Tools for Regression Testing Once the application code changes it is carried out its re-testing which is also called regression testing. This is done to make sure that everything is working correctly and that the changes did not result in any new software bugs. The destination of this type of testing is to verify that operating functions are not broken after the change of the code. It is important to conduct regression testing as often as possible (for example, after new software build), so that code modifications that damaged how application works can be quickly identified and fixed. As soon as there is something to test, then regression testing begins. Regression testing begins as soon as there is something to check at all. The regression test suite grows as the application moves ahead and test engineers add test cases that test new or rewritten code.  Soon the suite may extend to thousands of test cases that cover various application functions. Obvious...

User Acceptance Testing (UAT) For Websites

User Acceptance Testing For Websites The importance of user acceptance testing varies considerably. In some circumstances, it's founded a set of tests a program or Website must complete before delivery is acknowledged by the end personal. A more complete way to UAT contains the end customers at every level of the development process, and for the demands of determining business and e-commerce websites , this is the importance that should be used UAT is different from Quality assurance because it information issues that QA doesn't, like how easy and user-friendly a Website is to use rather than just the issue of whether the Website's significant features perform or not. It's possible to have a Website that goes all QA tests for basic functionality but is so challenging to use that it usually chases customers away. There are many Websites like this on the Online, and the earnings they cost organizations would probably secured the cost of adequate UAT several tim...

ISTQB Exam Question Paper, Part 4

ISTQB Exam Question Paper, Part 4 11. An incident logging system a only records defects b is of limited value c is a valuable source of project information during testing if it contains all incidents d. should be used only by the test team. 12. Increasing the quality of the software, by better development methods, will affect the time needed for testing (the test phases) by: a. reducing test time b. no change c. increasing test time d. can’t say 13. Coverage measurement a. is nothing to do with testing b. is a partial measure of test thoroughness c. branch coverage should be mandatory for all software d. can only be applied at unit or module testing, not at system testing 14. When should you stop testing? a. when time for testing has run out. b. when all planned tests have been run c. when the test completion criteria have been met d. when no faults have been found by the tests run 15. Which of the following is true? a. Component testing should be ...

ISTQB Exam Question Paper, Part 3

ISTQB Exam Question Paper, Part 3 1.Software testing activities should start a. as soon as the code is written b. during the design stage c. when the requirements have been formally documented d. as soon as possible in the development life cycle 2.Faults found by users are due to: a. Poor quality software b. Poor software and poor testing c. bad luck d. insufficient time for testing 3.What is the main reason for testing software before releasing it? a. to show that system will work after release b. to decide when the software is of sufficient quality to release c. to find as many bugs as possible before release d. to give information for a risk based decision about release 4. which of the following statements is not true a. performance testing can be done during unit testing as well as during the testing of whole system b. The acceptance test does not necessarily include a regression test c. Verification activities should not involve testers (reviews, in...

ISTQB Exam Question Paper, Part 2

ISTQB Exam Question Paper, Part 2 11 Consider the following statements i. an incident may be closed without being fixed ii. incidents may not be raised against documentation iii. the final stage of incident tracking is fixing iv. the incident record does not include information on test environments v. incidents should be raised when someone other than the author of the software performs the test a) ii and v are true, I, iii and iv are false b) i and v are true, ii, iii and iv are false c) i, iv and v are true, ii and iii are false d) i and ii are true, iii, iv and v are false e) i is true, ii, iii, iv and v are false 12 Given the following code, which is true about the minimum number of test cases required for full statement and branch coverage: Read P Read Q IF P+Q > 100 THEN Print “Large” ENDIF If P > 50 THEN Print “P Large” ENDIF a) 1 test for statement coverage, 3 for branch coverage b) 1 test for statement coverage, 2 for branch coverage c) 1 ...

ISTQB Exam Question Paper, Part 1

ISTQB Exam Question Paper, Part 1 1 When what is visible to end-users is a deviation from the specific or expected behaviour, this is called: a) an error b) a fault c) a failure d) a defect e) a mistake 2 Regression testing should be performed: v) every week w) after the software has changed x) as often as possible y) when the environment has changed z) when the project manager says a) v & w are true, x – z are false b) w, x & y are true, v & z are false c) w & y are true, v, x & z are false d) w is true, v, x y and z are false e) all of the above are true 3 IEEE 829 test plan documentation standard contains all of the following except: a) test items b) test deliverables c) test tasks d) test environment e) test specification 4 Testing should be stopped when: a) all the planned tests have been run b) time has run out c) all faults have been fixed correctly d) both a) and c) e) it depends on the risks for the system being tested...

How to write a System Test Plan?

How to write a System Test Plan? Imagine for a moment you've just finished a web application for a client. Swimming around within that application is 100 bugs. What proportion of those bugs would you say is acceptable for the client to find (e.g. 50, 30, 10)? The point is, those bugs are going to be found by someone, and its either going to be you or the client. You can think of it as a sliding scale, the more bugs the client finds, the more your creditability suffers and the more damage you do to the business relationship. In the martial arts there's a saying; "expect the best, but prepare for the worst". The US Navy Seals have a slightly more gun-ho version which goes; "The more you sweat in training, the less you bleed in battle." Notice how it says the ‘ less ' you bleed in battle, implying that if you enter into combat, you are going to get bloody. Software development is like this too, if you're going to create software, you are going to ...

What is Automated Software Testing Tools?

What is Automated Software Testing Tools? Software testing is one of the most important phases of software development process. Though hundreds of software applications are released every year by different companies, many of them fail to reach people as they are loaded with bugs and other errors. Since most of the companies are using software to automate their business process, quality is extremely important and any error in the software can be disastrous to the company. Hence, software testing is very important to maintain quality. Usually any piece of software is first tested for its effectiveness. Testers check if the application does its task. For example, an application meant for a retail store will be tested if does all calculations correctly. If it doesn't, that can lead to loss to the company. There are many types of software testing to ensure all aspects of product quality are ensured and that theapplication is fit for mass adoption. All software applications that we ...

ISTQB Foundation Level Specification

ISTQB Foundation Level Specification The International Software Testing Qualifications Board offer trainings and exams such as the ISEB-SWT2 exam or the ISTQB-ISEB Certified Tester Foundation Level. This examination is open to all who is involved in the testing of software. These people are testers, analysts, engineers, consultants, managers involved in testing and developers of software. The Foundation Level aptitude exam can also be applicable to anyone that understands testing of software, project and quality managers and other related fields. The usual content of the Foundation Level exam are the following topics: The Basic of Testing Importance of testing such as describing the reason that harms a software and testing as assuring quality Objectives of testing and differentiating it from debugging The testing principles The basic testing process Testing psychology Testing the Life of a Software Relationship of models and using samples The recognition of software ad...

What is ISEB-ISTQB?

What is ISEB-ISTQB Certification? ISTQB stands for "International Software Testing Qualifications Board". It is Belgium based International body legally established in the year 2002. Software testing professionals from all over the world joined hands in formulating standardized contents for further education in the field of Software Testing. It is a multiple-choice exam and is an education program offered in 38 countries. The ISTQB has come out with an International Qualification Scheme called "ISTQB Certified Tester". Presently there are two levels of exams leading to the specific levels of certification. Foundation Level Certification offers evidence that the certified person has a broad understanding of the key concepts & fundamental best practices of software testing. ) Foundation Level Certification: Name of this certification is "Certified Tester Foundation Level" (CTFL). This is the only one foundation level exam. This is an entry...

Statement Coverage and Pseudo Code, Question Papers

Statement Coverage and Pseudo Code, Question Papers. 1.       Given the following code, which is true: Read P Read Q IF P+Q > 100 THEN   Print "Large" ELSE   IF P+Q > 50 THEN      Print "Medium"   ELSE      Print "Small"   ENDIF ENDIF   a)       1 test for statement coverage, 3 for branch coverage b)       2 tests for statement coverage, 2 for branch coverage c)       2 tests for statement coverage, 3 for branch coverage d)      3 tests for statement coverage, 3 for branch coverage e)       3 tests for statement coverage, 2 for branch coverage 2.       Given the following: Switch PC on Start “outlook” IF outlook appears THEN   Send an email   Close outlook ...