ISTQB Foundation and Selenium Java Automation Testing
3.9 (127 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
6,185 students enrolled

ISTQB Foundation and Selenium Java Automation Testing

330+ Q&A from 2020 Test Takers- Live Projects in Selenium Java & .Net
3.9 (127 ratings)
Course Ratings are calculated from individual students’ ratings and a variety of other signals, like age of rating and reliability, to ensure that they reflect course quality fairly and accurately.
6,185 students enrolled
Created by Narayanan Palani
Last updated 7/2020
English
Current price: $129.99 Original price: $199.99 Discount: 35% off
8 hours left at this price!
30-Day Money-Back Guarantee
This course includes
  • 18 hours on-demand video
  • 78 downloadable resources
  • 2 Practice Tests
  • Full lifetime access
  • Access on mobile and TV
  • Assignments
  • Certificate of Completion
Training 5 or more people?

Get your team access to 4,000+ top Udemy courses anytime, anywhere.

Try Udemy for Business
What you'll learn
  • ISTQB Certified Tester Foundation Level (CTFL)
  • Software Testing
  • Testing Throughout SDLC
  • Static Testing-Statement and Decision Coverage
  • Dynamic Testing-Testing Techniques-EP,BVA,Decision Table,State Transition,Use Case Testing, White Box Testing, Error Guessing, Exploratory Testing
  • Functional Testing
  • Non Functional Testing
  • Change Related Testing
  • White Box Testing
  • Black Box Testing
  • Component Testing
  • Review Process
  • Test Management
  • Tools Support for Testing
  • Selenium
  • Selenium Webdriver
  • XSLT Reporting
  • TestNG
  • Errors,Defects,Failures
  • Basics of Software Testing
Requirements
  • Minimum experience or knowledge of Software Testing/Quality Assurance
  • 'ISTQB Certified Tester Foundation Level' is the exam conducted by ISQI. Author is independent to any boards or association and sharing his personal experience through this training program. It is highly recommended to refer the official syllabus from ISQI on ISTQB Foundations time to time since no accreditation or partnership associated to any board.
  • This Udemy course is built purely on Syllabus 2018 hence this course may not be suitable for old syllabus such as 2011
Description

This course will is geared to give you the skills you need to level up your career and get a high-paying job in Software Testing! To move up in your career you need to have solid experience that you can qualify when asked about. You need to know what you're talking about and that is what this course is all about.

The topics covered in this course dive deep into ISTQB testing concepts and will have you up to speed on what you need to know in no time! I do not fluff courses with pointless timefillers. Everything is designed to get you the information you need as quickly as possible.

***Exclusive price reduction and discounts are announced in facebook page 'Software Automation Testing Secrets Revealed'***

THREE MASSIVE SECTIONS:

  1. ISTQB Foundation Level Certification based Professional Training (Syllabus Version: 2018)

  2. Test Automation-Selenium Java

  3. Test Automation-Selenium .Net

Test Automation Sections:

'Test Automation-Selenium Java' section covers following topics using 21 Live Testing Projects:

  • Selenium Webdriver based Automation Framework using Java-Design and Development

  • Coding sample project on Web Page Automation

  • Core Automation Data Driven Framework using Excel Sheet based Test Data

  • Capture Screenshot Functions

  • Reusable Automation Components

  • XSLT Reporting

  • TestNG based Automation Execution

  • Excel Sheet based Control over Test Execution

  • Parameter based URL Access

  • Cross Browser Tests using Firefox,Chrome and Internet Explorer

'Test Automation-Selenium .Net' section covers following topics:

  • Automated Acceptance Testing using Behaviour Driven Development (BDD)

  • Specflow based BDD Test Design

  • Gherkin Basics

  • Features

  • Scenarios

  • Steps - Given, When, Then

  • Tags

  • Demo: Applying Tags

  • Demo: Commenting Lines

  • Data Tables in Steps

  • Data-Driven Scenario Outlines

  • Coding The Automation Steps

  • Installing The Required NuGet Packages

  • Step Definition Binding

  • Setting The Default step Definition Style

  • Adding New Steps

  • Deleting Steps

  • Running and Debugging Scenarios and step Definitions

  • Sharing step Definitions

  • Parameterization to Promote step Definition Reusability

  • Multiple and String params in A Single step Definition

  • Creating A step Definition with A Data Table

  • Scenario Outline step Definitions

  • Sharing and Maintaining State Between step Definitions

  • Automation Testing using Selenium Webdriver .Net framework in Visual Studio

  • Script using Five Live Projects on .Net based Selenium Specflow Automation Framework



PRACTICE SETS:

330+ ISTQB Repeated Questions are answered part of Practice Tests and it helped majority of the test takers before appearing in their foundations certification examination.

POPULARITY:

*****This famous Udemy course has been subscribed by 6,142 professionals across 118 countries until 4th April'2020. 39,595 minutes taught as a record breaking course within the last one year time!*****

LENGTH OF THE COURSE:

One among the top five courses with more than 17+ hours of training program which perfectly gives a real value for the money being spent! If you are still not satisfied after 17 hours classes, 100% money back is guaranteed!


WHAT IS ISTQB?

ISTQB:International Software Testing Qualifications Board

ISTQB foundations certification has been recognised worldwide and at least 673,000+ candidates certified by ISTQB until Oct'2019. Foundation level certification has been chosen by 87% professionals among the overall ISTQB certification test takers. Hence ISTQB has been made as a benchmark for initial assessment of any QA Resumes to screen and shortlist for Job Interviews.

Average salary of an QA/Test Lead/Automation Test Engineer is ₹ 5,93,458 per year in India (as per Indeed India website), €72K in European countries such as Germany (as per Glasdoor), $75513 in USA (as per payscale website), £42,535 in United Kingdom (as per Indeed UK website) and AU$74,980 in Australia (as per payscale website).


VERSION RELEASE NOTES:

May 03, 2020: What's New in Version 2.0

  • Added three sections on Selenium .Net using Specflow BDD


April 08, 2020: What's New in Version 1.1

  • Updated answer and speed of the video for the section video 'Syllabus Part 4.0 Equivalence partitioning-Age Group' based on participant inputs.




REVIEWS:

"A very must course for the QA engineer. It covers the topics that come in ISTQB paper. Go for it."

"Awesome materials and sessions to listen to them. It really helps with my foundation level examination. Thank you Narayana Palani. I will definitely suggest to my fellow members."

"Thank you for this course! It's well structured and contains very useful information for my certification preparation."

"I've been in the QA industry for 7 years and this course is teaching me things I didn't know. It makes sense, straight forward and gets to the point. the instructor is knowledgable and clearly a professional. I'm learning so much. Looking forward to completing the course and taking the big test!"

"This course has given me value addition in my learning phase of ISTQB. One amazing trainer with detailed explanations to each and every topic. Abundant questions and in depth coverage of the syllabus.Many Thanks! :)"

"It'a good course for going to certification"

"Very good content and briefly explained the all test techniques in simple way, easy to understand. Course content might be very good but what is the use if you have to wait forever and ever for videos to stream. I always come up with lot of interest to learn in Udemy course which is posted by Narayanan."

"An extremely helpful and informative course. The course is nicely designed keeping focus on entire ISTQB Foundation Course 2018 syllabus, it's contents are very well organised. All lectures are very clear, the instructor have good hold on the respective topics and explains the concepts nicely in understandable manner. Every section has relevant assignments and resources, which are extremely helpful. Instructor is very professional and pleasant to learn from. The videos used are of high quality, in terms of video and audio quality. I would strongly recommend this course..!!"


TRAINING METHOD:

Experience based 'ISTQB Foundations' training program explaining latest exam questions with details of how 'testing' is done in real time? (various udemy courses are already available with theory explanations hence this course is made focusing on sharing work experience,assignments and question samples)

As part of this ISTQB training, syllabus 2018 has been followed throughout the training program and author explaining about each section of the ISTQB syllabus with some of the repeated questions asked in previous years.

Assignments,external links to relevant documentations such as JIRA,Test Plans,Test Strategies are provided for users to understand with best examples in each section.

600+ ISTQB Questions are answered with useful justifications to selected questions that would help readers to download and prepare for the ISTQB exams whenever before appearance.

Relevant Youtube video links are provided for readers to listen to some useful videos such as test execution etc.

This Career Development Program(CDP) has been designed to accommodate fresh and less experienced Information Technology professionals to learn software testing and move to Test Analyst roles with ISTQB CTFL certification

REFERENCE:

  • Language: Strong Indian accent of English (not suitable for few participants if no prior experience in hearing the English in Indian accent)

  • Flow of Explanation: Based on prior testing experience rather than reading from slides.

  • Course Model: First focus is on Assignments since it is a Career Development Program (rather than focusing on getting the participants to clear exams and forget the concepts later on); Second focus is on recent exam questions and explanation based on prior software testing experience (there are hundreds of Udemy courses available with theory explanations of ISTQB and rarely any program provided with explanation of industry experience).

FREQUENTLY ASKED QUESTIONS:

Why this course has poor video/audio quality in regular intervals?

Our English Captions are reviewed and updated for majority of the videos. So they are not just autogenerated like rest of the udemy courses. When there is a poor internet connection or a loading time due to udemy server peak times,it is possible to get relay issues. Please keep the captions ON whenever you get this issue.


What is the reason behind some of the fast phased videos? Few videos goes in rapid speed and unable to understand clearly.

ISTQB contains several theory topics. Some of the areas are not that important but good to know. So these sections are updated with increased speed in order to manage time while completing the course. If you still need a second look at the section, decrease the video speed manually and enable caption ON for English in order to understand the sections better.

Why not the complete course taught with PowerPoint presentations? The trainer videos explaining his experience may be unnecessary to the topic.

The primary purpose of learning ISTQB is to excel in QA career. Also PPTs may not give a human touch without a trainer talking to you over videos. So this course contains mixer of ppt only and ppt+trainer discussions to give better explanations based on the nature of each topic.

Is this course suitable for viewing from desktop,laptop,tablet and mobile devices?

It is highly recommended to use a laptop or desktop to learn this course since the power point presentations are made compatible to laptop (screen size) only. Udemy do not support to download the section based attachments from mobile or handheld devices. Participants can view the course from Udemy app or mobile browser. But the experience is really good with a laptop or desktop screen. Even if you attempt to complete the course from udemy app or mobile browser, please watch it once from laptop/desktop for any attachments to download for your preparations.

DISCLAIMER:

YOUR USE OF UDEMY.COM (THE “SITE”),THIS COURSE (THE "COURSE") AND ANY AND ALL OTHER CONTENT, INFORMATION, PRODUCTS AND SERVICES OFFERED ON OR PROVIDED BY OR THROUGH THE SITE OR OTHERWISE BY NARAYANAN PALANI ("INSTRUCTOR") , IS VOLUNTARY AND SOLELY AT YOUR OWN RISK AND RESPONSIBILITY. INSTRUCTOR IS NOT RESPONSIBLE OR LIABLE FOR ANY INCORRECT ANSWERS, PARTIAL MATERIALS, OR ANY KIND OF PROBLEMS THAT MAY RESULT OR ARISE FROM YOUR USE OF THE SITE AND COURSE, ANY INFORMATION OBTAINED FROM THE SITE, AND/OR ANY OTHER CONTENT, INFORMATION, PRODUCTS OR SERVICES OFFERED OR PROVIDED BY OR THROUGH INSTRUCTOR, INCLUDING, VIDEOS,QUESTIONS AND ANSWERS,ASSIGNMENTS,PRACTICE TESTS,CAPTIONS,DOCUMENTS,POWER POINT PRESENTATIONS (COLLECTIVELY, THE “CONTENT”).

Copyright © International Software Testing Qualifications Board

Who this course is for:
  • Software engineers
  • Test engineers
  • Quality Assurance
  • Quality Engineers
  • Testers
  • Freshers
  • Test Automation Engineers
  • Product Owner
  • Business Analyst
  • Agile Testers
  • Software Engineer
  • Computer Engineer
  • Support Engineer
  • Fresher
  • Graduate
  • System Administrator
Course content
Expand all 92 lectures 18:08:00
+ Introduction Session
4 lectures 09:06

What is Software Testing?

“Software testing is a set of processes aimed at investigating, evaluating and ascertaining the completeness and quality of computer software. Software testing ensures the compliance of a software product in relation with regulatory, business, technical, functional and user requirements. Software testing is also known as application testing”

“An investigation on the product or service to improve the quality and find defects to report to stakeholders”

“A process of executing a programme or application with the intent of finding the software bugs”

“Software testing is a method of assessing the functionality of a software programme.”

“Software testing is the process of evaluating a software item to detect differences between given input and expected output.”

Though there is no set of generally accepted terminologies and guidelines worldwide, it is possible to refer the most valued glossary of software testing which are available online.

Set of detailed glossaries is provided online to facilitate the beginners.


Why Defects Occur in Software?

Software is written by information technology professionals who are human beings and are not devoid of committing errors. So mistakes are obvious on their part in some point of time in any of the work undertaken by them.

Human errors are common and are expected to be a part of the software when developed. But it costs more when identified late within the software projects.

Case1: How easy it is to cure to Cancer disease in the earlier stages?

As per the research, there is a high probability of survival if the disease is diagnosed and treated as earlier as possible.

Similarly, how easy it is to fix the defect within the software in the earlier stages?

Very easy: After reading the Software Requirement Specifications (SRS), Anderson identified incorrect flow and spelling mistakes within the feature names so he discussed with business analyst Rajavarman. Rajavarman was agreed with the mistake within the requirement and corrected it in the next version of the SRS document; hence, this incorrect feature is no longer existing in the project. If Anderson had missed reading about this incorrect feature here, he would have identified in later stages which would have made Martin (developer) to fix the code changes and it would cost Anderson to again spend more time to retest and identify its workability as required standards. But all this work have been diminished and removed just by finding the fault in the document review itself.

Refer: Design in the graph below. It is just 1x time of the total cost of the project taken by the defect fix.

Easy: Anderson testing the software which is under development process recently, and he identified a bug. It is easy for Martin (Developer) to fix it immediately and release the next version of code.

Refer: ‘Implementation’ in the graph below. It is just 6.5x times of the total cost of the project taken by the defect fix. Expensive defect comparing to the defects found in Design stage.

Difficult: Anderson testing the software before releasing to the customers, and he identified the bug. But the software has to be delivered within a week. Now, Martin has to fix the code and release to Anderson and he has to test and prove that the defect is not appearing anymore. All this has to be conducted within a week.

Refer: ‘Testing’ in the graph below. It is just 15x times of the total cost of the project taken by the defect fix. Expensive defect comparing to the defects found in Design and Implementation stages.

Very Difficult: Software has been released to customers and some of its functionalities were not found in workable condition. Now, Anderson tested it within his test environment according to the customer’s identification and realised that the bug is valid and needs to be fixed soon. Martin has no other option than releasing a new version of the software to customers with all the problems rectified.

Refer: ‘Maintenance’ in the section below. It is 100x times of the total cost of the project taken by the defect fix. Expensive defect comparing to the defects identified in earlier stages.


Phase in Software Development and Relative Costs to Fix the Defects

Design-1(Relative Costs to Fix the Defects)

Implementation-6.5(Relative Costs to Fix the Defects)

Testing-15(Relative Costs to Fix the Defects)

Maintenance-100(Relative Costs to Fix the Defects)


If Developer has strong development experience, why are the defects still happening in the software projects?

Martin has been working in developmental roles for the past twenty-five years and held a strong background of code development. But on the other hand, Anderson has been identifying some high priority bugs within his code in every cycle of the software project.

The primary reason for these defects is the ‘time limit’.

To deliver the code, ‘Under Increasing Pressure’ and ‘Tight project time lines’, a genuine mistake within the code is plausible.



How to rectify it?

Anderson has to be good enough to be trained in software testing and test coverage to identify bugs in its earlier stages of the software testing life cycle.


Software Testing-Four Key Objectives

Every test activities hold exclusive objectives and purposes to conduct list of test activities. But software testing itself has its own highest standards within the objectives and followed by every test specialist in testing projects. Some of them are listed here:

· ‘Finding Defects’:

Attitude of test specialists (comparing to developers) are found to be more defective and defended that the software has a lot of bugs in every test cycle. The defects are getting fixed to improve the quality of software. (not just raising the defects and leave it to developer’s hands. It is tester's responsibility to follow up on the defect and ensure that the defect is getting fixed.)

When high quality defects are raised or identified by the testers, they receive attention from test managers, development team and management of the organizations.

· ‘Gaining Confidence about the Level of Quality’:

Key stakeholders of the software projects are the business owners who trust on testers for their testing quality. Development managers coordinate with testing team to get the list of defects and get it fixed with the efforts of the developers. Then, testing team is requested to retest the fixes and ensure its functionality as updated to the present standards (retested). Hence, a lot of trust and value are evaluated on tester's profile. Testing managers manage and support entire testing team and watch out to help in every testing activity, hence, gaining confidence of testing team manager is the first priority for the tester, and then, the trust from project owner, development manager and key project managers are the key objectives of any test specialist.

· ‘Providing Information for Decision Making’:

Software test specialists are expected to provide a well written defect with all possible and relevant details about the defects during the test performance. When test reports are submitted to business owner, it should be meaningful, understandable and not cumbersome for non-technical stakeholders.

· ‘Prevent Defects’:

Identification of the defects is one of the sole objectives and preventing such defects from being occurred in testing projects in all possible ways such as review requirements and correcting the issues in documentation, hence, further defects can be eliminated.

Case1-Experience of Test Specialist:

There were some key defects raised with clear information on failures in one of the business critical applications for customers and the defects are under review process by business owners. They requested to have a detailed discussion on why such defects are raised. Post-detailed discussion, those defects led the project owners to take decision on stopping the project and redesigning the entire code of the software to deliver the high quality software to the customers. At the same time, this activity created a tension around development team (due to rework and unnecessary defects causing performance issues around developer's code quality); hence, most of the developers are curious to reduce such defect raising activity in future test cycles. So development team started coordinating with testing team members closely to review Software Requirement Specification, Design Documents which provided opportunities to testers on reviewing documents and providing their concerns and issues which are rectified immediately with the help of project owners; hence, further defects are prevented.

When the software came to retest in testers’ hands, it has been logged with further defect lists to get them fixed by developers. This story continues until getting supreme quality on the software within the given span of time. This process of raising high quality defects (no matter if developers concern on it or not) led to receive award from project owners on best individual contribution.

How Testing and Debugging are different?

Let us take the example of Cancer Treatments: PET Cancer Scan conducted to patients to identify the stage of the respective patients and then specialist in radiology or nuclear medicine analyse more on the medical test results and understand what kind of treatments are required to cure the patients. So both performing scan and analysing the test reports are two different activities and scan has to be performed prior to analysing the test report.

Similarly, software is tested by test specialists and defects are listed in software test results. Developers review the test results and investigate (debug) the code on the location of the error to fix the issues to resolve the failures, hence, testing and debugging are two different activities. Testing is to be done prior to debugging and both are done by two different specialists (tester: testing and developer: debugging).

How much Testing is enough?

If you assume that you have got a new functionality (example: Message Box in Mobile ) to test and found three hundred functional test cases available within the project, and now, you need to test this new functionality within two working days with the use of four mobiles as per the communication with the Project Manager.

Following are some of the important questions running in your mind:

1. How many test cases have to be tested?

2. How many defects can be identified possibly in these two days?

3. Is it possible to cover entire new functionality and related functionalities within these two days?

4. Why I have to test only in two days when there are three hundred test cases still to perform on the software?

5. How can I make sure that all the possible defects are identified and the functionality is working as expected in the given budget of four mobiles and two days?

6. What are the calculations that I have to make in order to perform these two days tests successfully?

The best suggestion is to pick the relevant test cases and run them for two days and identify its potential defects. If 45 test cases are relevant to message functionality (which has a high risk of finding new defects) and 20 additional test cases are relevant modules (may have defects due to the new functionality introduced), I would go ahead and test 65 tests within two days by splitting the work as 40 test cases per day. (There is a question on why 40 per day when 65/2 is 33: The real reason is to have a back up time for raising defects and retesting those defects on day 2 if possible)

So what matters in deciding this ‘how much testing is enough’?

Answer:

i. Level of Risk including Technical and Business product and project risk

ii. Project constraints such as time and budget

So what are not really matters when deciding ‘how much testing is enough’?

iii. Size of Testing Team

iv. Size of the Development Team



Software Testing Principles

1. Software Testing explores presence of defects

Though organizations value testing teams and their quality of defects raised in the testing projects but there is an important point mentioned: Do you think that developers don't know how to raise defects and find bugs within the software applications? Of course, they know it, but testers are the experts in finding the defects. If you are riding a bike on a packed road, do you think that you don't know traffic rules? Still, why traffic constables are appointed to monitor the traffic? This is to control the vehicles and monitor travellers on their activities. Similarly, developers do know how defects are identified, but testers are the strong and potential specialists to identify defects and manage those defects until getting fixed.

The first priority question is to realise why software testing and testing teams are required for a software project team? In fact, many start-up companies and small software companies' projects are getting delivered without even properly tested by software testers. Few start-up companies do not own testers within their software teams but the reality of high quality exist within software projects when testers are recruited with high quality background.


2. It is not possible to test exhaustive

An approach to test all possible combinations used for testing is known as Exhaustive testing. Anyone would prefer to test completely in such a way that all possible tests are covered, hence, full testing completion gives the satisfaction to business owners. But it cannot be considered as the right angle to look at the complexity.

It not only takes long time to test 'Exhaustive Testing', but it is not a suggested testing approach.

Why?

If you test the hotel booking application online, travellers may book and use the application in ten thousand possible ways probably, but if you have decided to test the entire combinations,

- How many resources are there to be deployed?

- How much cost involved?

- If any defects identified, do you repeat the complete combinations of exhaustive testing?

- Do you think market don’t change until you test complete combinations and release the product?

Due to complexities mentioned above, specialists always go in favour of important test combinations and relevant test combinations rather than testing everything (hence, exhaustive testing is impossible).

· What are the best approaches/options used to avoid exhaustive testing?

- Risk Analysis: Understand what are the high risk areas to test?

- Priorities: High/Medium/Low priority functionalities and pick high/relevant functionalities and medium/low whenever required.


3. Early Testing

Why the test should be performed early and why such approach required when development takes long time to prepare the software?

The actual answer is related to the defects and how fast those defects are needed to be fixed?

If the defects are identified earlier that gives a healthy environment of bringing high quality software on time.

Case1: Aravind is the leading software tester for the enterprise software who has been given the duration of seven weeks to test the software in seven cycles (one week per cycle).

He has found three minor/low priority defects for six cycles and identified two major/high priority bugs in the last week. Thus, project manager is left with remaining just 6 days to get the defects rectified and fixed. But the valuable questions are as follows;

- When Aravind is going to retest the fix and ensure that the fix is working as expected?

- If he finds the fix is open and needs to be fixed again, how many more days it takes to fix, retest and prove that the latest fix is working fine?

Due to the situation above, there is a fair chance of extension in the delivery date of the software for further testing and it impacts overall cost and customer satisfaction on the late delivery of the software.

What needs to be done to avoid the situation of late delivery of the software and last minute defects?

Test Early!


4. Defect Clustering

“Small number of modules contain high number of defects and lead to operational failure”

Case1: Rajavarman tests 20 modules of ABC bank’s payment system and found 55 defects within the account details module itself. The total number of defects found in the entire functional testing is 57 which show that the number of defects within account details module is higher than 19 other modules.

These issues cause the operational failures, hence, his manager Srinivasa suggests to perform a Defect Retest of all 55 fixes of the defects and repeat the tests on account details module to 100% coverage. This is to ensure that the account details are working as expected and no more bugs are introduced by fixing the 55 defects, hence, this particular module is clustered with high number of defects. Defect clustering creates the alarm to test management to concentrate more on the specific modules to validate and ensure the capturing and fixing of all the defects before proceeding to the next stage of the testing process.


5. Pesticide Paradox

“If same tests are being repeated in every Regression Cycle, the chances of the occurrence of new defects in AUT is less.”

Case1: Jagan looked after the automation tests and has designed 1800 automation test cases using selenium to run in every drop of the product release. He is recycling the use of the same tests for every drop (as expected in Regression Tests).

In the very first drop, he found 130 defects which has become single digit of defects in further drops. In fact, Drop 19 produced no defect after his Regression Test Execution. The real question is relying on the test cases and when they are really designed. If the test cases are not updated over time, there is no point of reusing them as the expected defects are already raised or discussed with development team, and there is no use of this automation test pack, hence, this situation is a named as pesticide paradox. Jagan started updating the test scripts to match with the latest user stories and run them as part of test cycles which led him to identify new defects. Thus, redesigning and improving is the ideal solution for pesticide paradox.


6. Testing is Context Dependent

Case1: Karthick has been working for medical software in government hospitals and his work is to validate the softwares used for scanning equipments. Similarly, Apoorv is working on the testing team of ‘scanning equipment ordering system online’ to contact vendors and distribute the machines across different hospital branches. Though both of them deal with scanning system related software, Karthick’s work is critical and dealt differently than Apoorv’s testing process due to the safety-critical software involved in medical domain where as Apoorv’s work is pretty much related to eCommerce/CRM applications. So the test cycles followed and reviewed process involved in both the testing activities are different in nature.

7. Absence of Errors Fallacy

Case1: John Trench is a test lead for the telecommunication projects which are involved in 3G technologies. His is assigned with the work to deliver the quality reports and list of defects identified. Due to the unwanted situations, project deadline was crossed and he delivered list of defects only after 3 weeks of deadline provided. The situation at the customer front has been moved towards 4G and there remains no need of 3G-based software systems what John has been getting his team to work on. Hence, no matter how much defects/errors are reported in a test cycle, if it is not relevant or useful in the way customers wanted, it is the situation known as Absence of Errors Fallacy.


Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Preview 01:31
Learn ISTQB-Make Your Resume Strong
01:27
+ Testing Techniques (Solvable Questions Expected)
24 lectures 01:02:34
Syllabus Part 4.0 Test Techniques, 4.1 Categories and 4.1.1 Test Techniques
02:53
Feedback Matters!
00:44
Syllabus Part 4.0 Equivalence partitioning-Money Order System
06:12
Syllabus Part 4.0 Equivalence partitioning-Customs Duty
03:09
Syllabus Part 4.0 Equivalence partitioning-Booking System
02:18
Syllabus Part 4.0 Equivalence partitioning-Age Group
01:33
Syllabus Part 4.0 Boundary Value Analysis-Additional Entrance Fee
06:16
Syllabus Part 4.0 Boundary Value Analysis-Garden Irrigation System
01:48
Syllabus Part 4.0 Boundary Value Analysis-Group Size
02:55
Syllabus Part 4.1.2 Categories of Test Techniques and Their Characteristics
02:46
Syllabus Part 4.2 Black-box Test,4.2.1 Equivalence Partitioning and 4.2.2 BVA
03:51
Syllabus Part 4.2.3 Decision Table Testing
03:20
Reference: https://en.wikipedia.org/wiki/Decision_table
Decision Table Exercise
1 question
Syllabus Part 4.2.4 State Transition Testing
02:50
Syllabus Part 4.2.5 Use Case Testing
01:03
Syllabus Part 4.2.5 Use Case Testing Basics
02:33
Syllabus Part 4.2.5 Use Case Testing on Library Management System
03:24
Syllabus Part 4.3 White-box Test Techniques
02:22
Syllabus Part 4.3.1 Statement Testing and Coverage
01:58
Syllabus Part 4.3 Statement and Decision Coverage -Case Study
01:22
Syllabus Part 4.3.2 Decision Testing and Coverage
02:27
Specification based analysis
4.3.3 The Value of Statement and Decision Coverage
1 question
Syllabus Part 4.4 Experience-based Test Techniques
01:45

Attached Tab sequence related video on accessibility test help to understand error guessing while pressing Tab using keyboards! That helps to explore more keyboard strokes to identify similar defects (after having a thought process of error guessing)

Syllabus Part 4.4.1 Error Guessing
01:36
Syllabus Part 4.4.2 Exploratory Testing
01:49

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 4.4.3 Checklist-based Testing
01:40
+ Fundamentals of Software Testing
15 lectures 01:08:50

Topic:Basics of Software Testing

Attachments: 'JAWS testing on Sequence and Audio Control.flv' has been provided to understand an example test for web accessibility; The test has been conducted with a tool called 'JAWS' which is commonly used by users with disabilities such as visual impairment. So tester's objective is to identify any difficulty for such users during this testing!

Preview 06:13
This basic exercise will help the participants in writing simple test cases to improve their testing knowledge and experience!
Write a Test Case!
3 questions
Syllabus Part 1.1.1 Objectives of Software Testing
05:25
Testing and Debugging Quiz
1 question
Syllabus Part 1.2.3 Basics on Errors to Defects and Defects to Failures
01:23
This exercise will help the participant to learn how to raise a defect!
1.2.3 Exercise to report a defect
1 question
Syllabus Part 1.2.4 Defects, Root Causes and Effects
03:20
Syllabus Part 1.3 Seven Testing Principles
08:55
Syllabus Part 1.3 Seven Testing Principles Repeated Questions
03:35

Test Takers Inputs during April 2019 Exams (2018 Syllabus):

Experience Based Questions are asked part of Test Process based Questions



Syllabus Part 1.4 Test Process
09:05

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 1.5 The Psychology of Testing
02:20
Basics:Why Testing is necessary?
04:56
Basics:Error-Fault-Failure
01:46
+ Testing Throughout the Software Development Lifecycle
14 lectures 39:45
Syllabus Part 2.2.1 Component Testing
02:39
Component Testing Quiz
4 questions
Syllabus Part 2.2.1 Component Testing -Statement Coverage and Decision Coverage
03:05
Learn on how to calculate tests cases for statement coverage and decision coverage
Statement and Decision Coverage Exercise
2 questions
This exercise has been asked to recent test takers during 23 June2019 online tests
Statement and Decision Coverage Exercise on Nested If Combination
2 questions
Syllabus Part 2.2.2 Integration Testing
02:47
Syllabus Part 2.2.3 System Testing
04:17
Syllabus Part 2.2.4 Acceptance Testing
02:15
This assignment will help the participants to differentiate functional test cases (used in system testing,regression testing and system integration testing) and user acceptance test cases (used in UAT Testing)
Acceptance Testing- Test Case Exercise
1 question
Syllabus Part 2.3 Test Types
01:04
Syllabus Part 2.3.1 Functional Testing
04:31
This test execution exercise will help participant to understand the way how the tests are made PASS or FAIL based on the current state of the application during testing cycle
Functional Testing-Test Execution
2 questions
Syllabus Part 2.3.2 Non-functional Testing
02:14
Web Accessibility Testing is brought into scope when customers need special assistance such as visually challenged,physically challenged and need of accessible software. Example: If a customer is 100% blind,he or she may use a tool called JAWS to access the website and hear the voice over!
Non-functional Testing-Accessibility Testing Exercise
1 question
Syllabus Part 2.3.3 White-box Testing
02:59
Reference for Cyclomatic Complexity: https://en.wikipedia.org/wiki/Cyclomatic_complexity
White-box Unit Test Exercise
1 question
Syllabus Part 2.3.4 Change-related Testing
01:49
Syllabus Part 2.3.4 Change-related Testing-Additional Discussion
02:29
Syllabus Part 2.3.5 Test Types and Test Levels
03:11

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 2.4 Maintenance Testing
02:20
+ Static Testing
9 lectures 31:59
Syllabus Part 3.1 Static Testing Basics and 3.1.1 Work Products
03:10
This assignment will help the participant to understand on how to perform review on a document such as test plan
Informal Review-Test Plan
1 question
Syllabus Part 3.1.2 Benefits of Static Testing
03:50
This assignment will help the participant to get an opportunity to review test scenarios for the training website which has been due for manual testing
Informal Review-Test Scenarios
1 question
Syllabus Part 3.1.3 Differences between Static and Dynamic Testing
05:04
Static Cyclomatic Complexity is wide used concept in Static Testing and many questions were asked in the past from this area. V(G)=Cyclomatic Complexity E = the number of edges of the graph. N = the number of nodes of the graph.
Static Testing-Cyclomatic Complexity
1 question
This exercise will help participant to understand what developers might do when they developed a small web page to perform dynamic testing (code scan)
Dynamic Testing-Code Scan for Accessibility Violation
2 questions
Syllabus Part 3.2 Review Process
01:14
Syllabus Part 3.2.1 Work Product Review Process
05:19

Important(Repeated) Question:

Which expression best matches the following characteristics or review processes:

1. led by author

2. undocumented

3. no management participation

4. led by a trained moderator or leader

5. uses entry exit criteria


s) inspection

t) peer review

u) informal review

v) walkthrough


a) s = 4, t = 3, u = 2 and 5, v = 1

b) s = 4 and 5, t = 3, u = 2, v = 1

c) s = 1 and 5, t = 3, u = 2, v = 4

d) s = 5, t = 4, u = 3, v = 1 and 2

e) s = 4 and 5, t = 1, u = 2, v = 3


Answer: B

Syllabus Part 3.2.2 Roles and responsibilities in a formal review
04:51
Syllabus Part 3.2.3 Review Types
02:05
Syllabus Part 3.2.4 Applying Review Techniques
03:12

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 3.2.5 Success Factors for Reviews
03:14
+ Test Management
11 lectures 26:55
Syllabus Part 5.0 Test Management and 5.1.1 Independent Testing
02:58
Syllabus Part 5.2 and 5.2.1 Purpose and Content of a Test Plan
03:25
Please take a sample project for testing and write a Test Plan with your assumptions. Test Plan Form: https://docs.google.com/forms/d/e/1FAIpQLSeOpn7N8EaANdpARafhOUy4PWVma8chTYQetKjaDW3AGbJL8A/viewform?usp=sf_link
Test Plan Assignment
1 question
Syllabus Part 5.2.2 Test Strategy and Test Approach
01:21
Take a sample project and analyse on how to write test strategy for the project? Example: eCommerce Shopping Website
Test Strategy Exercise
2 questions
Syllabus Part 5.2.3 Entry Criteria and Exit Criteria (DOR&DOD)
02:59
Syllabus Part 5.2.4 Test Execution Schedule
02:33
5.2.5 Factors Influencing the Test Effort
02:48
Syllabus Part 5.2.6 Test Estimation Techniques
02:11
Syllabus Part 5.3 Test Monitoring and Control
03:09
Syllabus Part 5.4 Configuration Management
02:14

Risk Based Testing

Carrying out software testing activities by considering risk as the primary theme of the project is Risk Based Testing which aims to identify potential risky defects and improve the quality of the Application Under Test by fixing such high risk defects.


Understanding Risks:

Risks are the uncertainties expected in future with probability of occurrence and expected potential losses as outcome, hence, it impacts the software testing projects, and right mitigation actions are expected to take care to overcome such risks. Risks can be anything which cause the losses such as financial losses or losses of customers or even the corporate brand image damage to the product.

Identifying loss making risks and controlling with right action plan are the key elements in every software testing project.

Formula:

Risk=Damage to the project*Probability or Occurrence

Example:

Risk of the Login Failure of Web Page within project AB=Lost of 800 CAD per failure*10 times occurrence expected in current year=8000CAD Loss due to the Risk for the current year


When Risk Based Testing is considered as a Best Fit?

If the projects are facing challenges due to time, cost, resource, environment, hardware or frequently changing requirements or anything which challenges the project delivery, this result in implementing Risk Based Testing to such projects to carry out testing by considering those risks as primary motivator to the project.

Case1: AB Ltd is short of 140 lakhs to carry out last phase of the testing project to complete Regression Tests, hence, Test Manager Helen Mitchell decided to implement Risk Based Testing to carry out limited number of high risk test cases within the time of the test execution.

Case2: Mobile Product company is planning to release next version of the android phone which will attract at least 1.2 billion buyers across the world. But there is a potential risk that the defect identified earlier while testing that causes damages to at least three functionalities of the mobile features, and they are consistent failures as well. Henceforth, the testing team has been following Risk-based approach on those high priority defects and on their defect fixes and testing around the affected features to get released in the next 3 weeks time.


Types of various risks and their potential impact:

Every risk has been carefully identified, analysed, classified and controlled before actual execution of the programme.


Following are some of the important classification of risks:

· Schedule Risk:

Failure to meet the deadlines of delivery is a crucial risk in software projects. There are many critical aspects of what can go wrong when tests are estimated?

Incorrect calculation of time estimation leads to extending the project time to complete the test cycles and less customer satisfaction.

When resources are not monitored and controlled, project delivery get affected due to unexpected leaves causing absence of resources, no or irregular training causing poor performance, irregular management result in less productivity etc.

Failure to identify high priority defects and finding such important defects in the last minute leads to delay in the testing cycle completion.

Especially project scope has to be determined in the initial stage of the project and amendment of such project scope (usually common in complex customer projects) creates additional test scope for the testing team.

Note: Refer ‘Software Automation Testing Secrets Revealed’ Publishing Date 12 Feb 2016 - Chapter 7: Test Estimation on various Test Estimates and respective calculation.

Case: Surendar Singh, a test manager of Aditi Solution Tech. Ltd. has planned three weeks testing of 15 working days to complete the testing cycles of approximately 850 test cases. It has been planned as follows: 850/(15*4)=14 test cases per person/per day, henceforth, he has targeted at least 15 test cases to be performed to meet the deadline. Paul from the team has gone in surprise leave on the very first week for 4 days and this would have affected 4*14 test cases =52 test cases of the project in a particular module. As a twist to the story, another team staff has gone in sick leave for two days in the middle of the test cycle which created additional backlog of 28 test cases on top of 52 existing backlogs, and Surendar has no other option than increasing the duration of the project at the last week which has created tension around the delivery date. This situation shows a clear example of poor planning from the test management. If leaves were organized earlier and Surendar had planned at least 16 working days of tests to include 2 days as backup, then it would have sort out the leave issues on time. Because the total backlog of tests 80 (means 52+18) would have executed with the help of last working day availability.


· Budget based Risk

Test manager estimates budget for the complete testing assignments and proposes the total cost to the project management. If such budget is gone wrong in any possible way, it impacts with high risk to the project delivery.

When project expenditure has been increased due to number of defects raised in the last cycle of the testing, it is fairly possible that the risk is very high to the project and it may affect the delivery of the project after testing.

Especially, increasing project scope during the testing cycles creates additional impact on the ongoing project and increasing risk of failure to high.

Case-wrong budgeting: Rachael has been looking after her testing team for the last three years and her estimation has never gone wrong at all. As a test lead, she looked after the complete six member automation testing team and there is no test manager in the start up organization. She estimated budget of 200 million for the next agile testing project which span across seven months duration in the end of the next year. When the project started, there was a resource constraint and increased license fee for test automation tools (just few days ago when extending the licenses) which caused 43 more million to the overall testing budget, and eventually, it resulted in getting the work outsourced from a new partner of the organization (which is the decision taken by the owner of the organization). The primary reason for the wrong budgeting is not the incorrect calculation but the preparation of budget one year before the actual project being initiated which created the huge gap between expectation and reality.

Case-Cost Overrun: Satyadip is the project manager who looks after testing team’s cost and budget estimation, and his estimation of budget overrun due to the hardware problems of the project and additional hardware are required in order to continue testing. Senior managers of the organization denied to allow any further cost in addition to the planned budget of Satyadip, which is a critical risk to the project and the testing activities are put on hold until the approval has been given to buy and replace the existing repaired hardware. The real mistake is not fully on the budget but on the investigation before arriving at the final calculation of the budget. It is suggested to get the hardware reviewed by technical engineers on their steady state and warranty period in order to include hardware costs to the budget.

Case-Project Scope Expansion: Business Analyst of the Mobile Automation Testing Project raises the alarm to stakeholders that the scope of the project is now increased due to new regulations of the telecommunication department of government. Now, the test manager of the project, Mr. Lahiri, suggests the increase of 23 million in the overall test automation programme for the next two years due to this impact. So the real cause to this high risk of increased cost is due to socio-political-economical-legal-technical impacts (called S.P.E.L.T).


· Operational Risk

Software testing projects plan to improve the quality standards by implementing industry’s best practices as new set of processes. If there is a mistake in implementing such processes, it creates lot of expenses to overall project budgeting. Hence, such operational risks lead to project failures in most of the occasions.


How Risk-Based Testing is benefited with Automation Tests

A number of Automation Tests with various priority, severity combinations help automation team to choose right set of test suites to run in test cycles. Also automation frameworks are the straight solutions to adapt as part of Risk-Based Testing rather than choosing 100% manual testing to complete tests which doesn’t fit to short time in most of the projects.

Syllabus Part 5.5 Risks and Testing
01:05

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 5.6 Defect Management
02:12
This exercise will help the participant to understand how a defect management system constructed based on the testing types and answering to questions would help getting more confidence in the certification exam
5.6 Defect Exercise
2 questions
+ Tool Support for Testing
4 lectures 13:05
Syllabus Part 6.1.1 Test Tool Consideration and Classification
04:06

Use some of the well built and available selenium frameworks to practice and explain the framework oriented questions(in job interviews) from,

Java Based Selenium Frameworks Available:

· https://github.com/jaypee2286/Java-SeleniumSample

· https://github.com/pathimanoj/Google/tree/master/google

· https://github.com/im-zeeshan/serenitybdd-automation-framework/blob/master/src/test/resources/stories/AcceptanceTestSuite/Capability/Feature/STR101-LookupADefinition.story

· https://github.com/techGen/WebDriver_Framework

· https://github.com/rkumar2131/MineSweeperAutomation

· https://github.com/SkillsFundingAgency/specflow-selenium-framework/tree/master/Specflow_Selenium_PO_Example2/Features

· https://github.com/irishshagua/web-automation-sample-framework

· https://github.com/hemano/Automation_FW_Cucumber

· https://github.com/agalyad/WebDriver_Java_TestNG_Ant

C# Based Selenium Frameworks Available:

· https://github.com/michaelthecsguy/PayoffAutomationJUnit

· https://github.com/kapilsethi/AutomationUsingWebDriverAndPageObjectPattern

· https://github.com/agalyad/WebDriver_C_NUnit

Java Script Based Selenium Frameworks Available:

· https://github.com/Matt-B/cucumber-js-selenium-WebDriver-example

Python Based Selenium Frameworks Available:

· https://github.com/gowtham88k/selenium_python

· https://github.com/Rosalita/Selenium

· https://github.com/hermanwahyudi/selenium/

· https://github.com/shahriarqureshi/Python

Ruby Based Selenium Frameworks Available:

· https://github.com/testwisely/agiletravel-ui-tests

General Selenium Related Frameworks Available:

· https://github.com/jenglezou/chilaca

· https://github.com/yuliabro/WebDriver

· https://github.com/3vilvetal/WebDriver/tree/master/HelloWorld

· https://github.com/camiloribeiro/cello

· https://github.com/IntelligentSigma/selenium-test-automation-framework

· https://github.com/axatrikx/axa-framework

· https://github.com/Webaib/Selenium-LWF

· https://github.com/Natalya11444/Cucumber-Selenium-JUnit-Test-Framework

· https://github.com/Natalya11444/Selenium-TestNG-Test-Framework

REST API Based Selenium Frameworks Available:

· https://github.com/kvyasHacks/APITestAutomationFramework/tree/master/nasa-test-base

· https://github.com/lnikod4s/automation-selenium-testing-framework

· https://github.com/michaelthecsguy/PayoffAutomationJUnit

Appium Based Framework Available:

· https://github.com/agalyad/iOS_Appium_Java

Selenium using Excel VBA -Projects Available:

· https://codingislove.com/browser-automation-in-excel-selenium/

· https://github.com/florentbr/SeleniumBasic

· http://www.makeuseof.com/tag/how-to-automate-firefox-or-chrome-with-vba-and-selenium/

· https://www.youtube.com/user/xtremeExcel/search?query=selenium

Excel VBA and Internet Explorer Based Automation Framework Available:

http://automatetheweb.net/

Selenium Queries can be answered at:

· http://grokbase.com/g/gg/selenium-users

Syllabus Part 6.1.2 Benefits and Risks of Test Automation
02:52
Syllabus Part 6.1.3 Test Execution and Test Management Tools
02:12

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Syllabus Part 6.2 Effective Use of Tools
03:55
This exercise will help the participant to understand the procedures to choose right toolset for the projects
6.2 Tool Selection Exercise
1 question
+ Few Last Steps-ISTQB Certification Preparation
2 lectures 02:26
Understand Exam Appointment Scheduling Steps
01:13
Practice Tests CTFL
250 questions

These questions are based on exam code: 'CTFL_Syll2018' which is explained in Lecture 66. Thanks to test takers recently for those inputs on exam question format.


Please refer the ISTQB CTFL Glossary for Reference:

https://www.istqb.org/downloads/category/20-istqb-glossary.html

CTFL Practice Test based on June 2019 Question Paper
87 questions

Latest Inputs from ISTQB CTFL Test Takers:

  • Questions were distributed across following chapters:

Chapter/Section 1: 8 Questions

Chapter/Section 2: 5 Questions

Chapter/Section 3: 5 Questions

Chapter/Section 4: 11 Questions

Chapter/Section 5: 9 Questions

Chapter/Section 6: 2 Questions

  • Experience Based Questions are asked part of Test Process(Section 1.4) based Questions

  • Less questions were asked from areas such as Static Analysis with tools(Section 4),White box coding related areas.

This test has been taken from India part of 2018 Syllabus as on April 2019

Note:

'Section 8- Conclusion' contains an 'EndNote' video followed by important attachments such as 600 Q&A of ISTQB from the last 10 years,CV preparation tips and few important topics as attached downloadable documents-don't forget to save them

Your time is valuable for us and these materials will help clinching the success soon! You are few steps away from taking ISTQB certification exam with the help of our premium course materials which is a key to strong QA career-make sure you get complete confidence before appearing for the exam and get 100% and nothing less!


After watching the 'End Note' video,there will be an option to ✍review the training program and please don't forget to rate us! We would love to see five star ratings ✯✯✯✯✯ as a recognition for our hard work

Enlightening Information(DO NOT FORGET ATTACHMENTS)
01:13
+ Test Automation-Selenium Java
5 lectures 10:02:25

Code Download Location:

https://github.com/narayananpalani/testautomation


Following topics are included in the session:

· Selenium Webdriver based Automation Framework using Java-Design and Development

· Coding sample project on Web Page Automation

· Core Automation Data Driven Framework using Excel Sheet based Test Data

· Capture Screenshot Functions

· Reusable Automation Components

· XSLT Reporting

· TestNG based Automation Execution

· Excel Sheet based Control over Test Execution

· Parameter based URL Access

· Cross Browser Tests using Firefox,Chrome and Internet Explorer

Basics-Test Automation using Selenium-Java-Discussions Day 1
02:02:22
Basics-Test Automation using Selenium-Java-Discussions Day 2
01:34:56
Basics-Test Automation using Selenium-Java-Discussions Day 3
01:49:18
Basics-Test Automation using Selenium-Java-Discussions Day 4
01:44:19
Basics-Test Automation using Selenium-Java-Discussions Day 5
02:51:30
+ Test Automation-Selenium .Net
3 lectures 02:51:32

Specflow Specific Presentations:

Session1:

http://prezi.com/6fhrbye6pdob/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session2:

http://prezi.com/faelbeufldfy/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session3:

http://prezi.com/kiwsyghiqbe0/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session4:

http://prezi.com/2x7rowgdrvlm/?utm_campaign=share&utm_medium=copy&rc=ex0share

http://prezi.com/805gm5sktpnu/?utm_campaign=share&utm_medium=copy&rc



Projects:

https://bitbucket.org/cebartling/presentations/src/3037e9646560?at=default

https://github.com/dchetwynd/Behaviour-Driven-Development-with-SpecFlow

https://github.com/techtalk/SpecFlow

https://github.com/baseclass/Contrib.SpecFlow.Selenium.NUnit

https://github.com/alexmelkor/FinanceIUATe


Basics-BDD Specflow and Selenium .Net Testing-Part1
57:18

Specflow Specific Presentations:

Session1:

http://prezi.com/6fhrbye6pdob/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session2:

http://prezi.com/faelbeufldfy/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session3:

http://prezi.com/kiwsyghiqbe0/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session4:

http://prezi.com/2x7rowgdrvlm/?utm_campaign=share&utm_medium=copy&rc=ex0share

http://prezi.com/805gm5sktpnu/?utm_campaign=share&utm_medium=copy&rc



Projects:

https://bitbucket.org/cebartling/presentations/src/3037e9646560?at=default

https://github.com/dchetwynd/Behaviour-Driven-Development-with-SpecFlow

https://github.com/techtalk/SpecFlow

https://github.com/baseclass/Contrib.SpecFlow.Selenium.NUnit

https://github.com/alexmelkor/FinanceIUATe


Basics-BDD Specflow and Selenium .Net Testing-Part2
56:35

Specflow Specific Presentations:

Session1:

http://prezi.com/6fhrbye6pdob/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session2:

http://prezi.com/faelbeufldfy/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session3:

http://prezi.com/kiwsyghiqbe0/?utm_campaign=share&utm_medium=copy&rc=ex0share

Session4:

http://prezi.com/2x7rowgdrvlm/?utm_campaign=share&utm_medium=copy&rc=ex0share

http://prezi.com/805gm5sktpnu/?utm_campaign=share&utm_medium=copy&rc



Projects:

https://bitbucket.org/cebartling/presentations/src/3037e9646560?at=default

https://github.com/dchetwynd/Behaviour-Driven-Development-with-SpecFlow

https://github.com/techtalk/SpecFlow

https://github.com/baseclass/Contrib.SpecFlow.Selenium.NUnit

https://github.com/alexmelkor/FinanceIUATe


Basics-BDD Specflow and Selenium .Net Testing-Part3
57:39