Category: ISTQB

Why Testing is important:

Success Contributions:

Use appropriate test techniques with appropriate level of expertise and test level and at specific point in SDLC
To work closely with BA/BSA so the testers do requirement reviews in Waterfall and User story refinement in Agile
To work closely with Developers to understand the functionality expected in their view and create effective test cases.
To work closely with to review the design understood and in progress from their point before the application is released in the QA Environment.

The above items will help the org to get the app tested before release and get the defects detected earlier in the SDLC which saves cost of fix if it’s found later the SDLC. Let say for Ex: if a fix on the requirement needs a BSA /BA to check and update may be 4 hrs effort, for developer to fix may take 0.25 days or 3-days as well.

Static and dynamic testing create diverse types of failures.

Quality Assurance vs Testing

Quality- find as many failures as possible then fix and product goes live with quality.
QA–Quality Assurance team which defines the process measures or the steps for the quality to be achieved.
QA- define.
QC–Quality Control team involving diff test activities- like TC prep, TC Execution – Defect logging/report to control defects and improve quality.
QC- Action.
Testers come in part of Quality control- who do the ground level action which is defined by QA.

Error – Defect – Failures
Errors – same as mistakes – Human action that produces an incorrect result.
Fault – known as defect or bug (informal name) – deviation between the expected and actual
Failure – generally when a test case fails while executing the test case- testers are responsible to identify failures.

Causes of Software defects:

1. All – Time Pressure – limited timeline or sparse number of resources for the launch date of the application.
2. All – Human – error prone in general and not machine.
3. All – Inappropriate person- inexperienced project participants
4. All – Miscommunications between the participants-> conveying the correct info and making sure the other person is understood!
5. All – Code complexity – more complex the flow may go wrong, need to be more cautious on these flows
6. All – Misunderstanding intra systems- internally when the modules are connected what is the requirements, ex: Module 1-> module2, module2->module3 inter system- other systems speaking to each other
7. All – unfamiliar technologies- built and having releases every day!

Fundamentals of Testing – The most basic but important part of the foundation level examination. the below points marks the 5 fundamentals.

1.1 What is Testing (K2)?

1.2 Why is testing necessary?

1.3 Seven testing Principles

1.4 Test Process

1.5 The Psychology of testing

1.1 What is Testing? (K2) –

Testing has a wide range of understanding and definitions, the common one is the tester executes the steps of an application flow and check the actual behavior of the application is working as expected as per the requirement, finding bugs, there are few other things to consider as well, as provided below:

STLC starts with static testing, the document gathering like any work product (Requirement, Specifications, User story) created in the STLC. testing done form the requirement phase, the review helps in preventing the defects even before the development is started Many other activities other than test execution in STLC.

Objectives of testing:

Find defects – By writing and executing the test cases on the application under test and find maximum defects as possible.

Gain the confidence on quality – By executing the positive scenarios QA team will have the confidence, until we have confidence, we cannot give go ahead on the release.

Note: Ask for extra time if any critical info is not covered, to avoid product failure in the market that may incur losses like business or human lives etc..

Providing information – Provide status on the progress, typical defects and fix status and artifacts that covered all critical areas so the decision/ go-ahead can be taken by the Management, stake holders for release.

Preventing defects – more information in terms of review of the work products, getting involved on early stage, testers can find more defects on early stage can help in minimizing the defects during the future phases of app releases.

Review of Work products – reviewing the docs like Requirements and specifications even when they are in draft status, can be called as static testing as well.

Verify all the requirements are met and none is missed – its the base and important part , by using all the test techniques so dev team has delivered on all requirements.

Reduced risk level – critical parts covered by the test cases so the risk is reduced and measures if a risk is suddenly pops up!

Comply with legal or regulatory requirements and standards – in Business Requirement these info has to be mentioned – ex: other than functional there may be may other requirements to be taken care of, there are few non functional requirements as well. A tester should be using a diff approach while validating a Banking application or a ecommerce or a security based application.

Classification of Testing

Static – Documents created as a part of STLC, and do not involve any execution ( flow charts, algorithms, Business Requirements, Specifications) once the static testing is done, documentation for the levels of testing can be initiated. this process is called Review

1. Formal Review
2. Walkthrough
3. Technical Review
4. Inspection

Dynamic – test execution of application under test – can be called as Levels of testing

1. Unit
2. System
3. Integration
4. UAT etc..

Debugging and testing

Testing – Done by the tester, to identify the defect.

Debugging – Done by the developer, to analyze the defect, finds the root cause and remove the root cause(FIX)

Introduction:

About – International Software Testing Qualifying Board – certify individuals for testing understanding and learnings across the globe can take up the exams with respective boards.

Certifications – Many new versions are added earlier only 3 were there now we have 4 paths. Foundation level certification is the pre-requisite for the rest of other certifications to be taken.

Local Body – CSTB (Canada), ISQI, ISTQB.in etc.. based on the locale/country it can be found from their website.

Who can appear – Any who has the basic understanding of the testing, no pre-requisite is there for applying for the Foundations level exam.

Cost – around 200 USD

Valid – Life time (write once use it for life time)

EXAMINATION:

40 multiple choice questions with only one correct answer no conflicts are expected.

Total time for 40 questions are 60 minutes and 65% is the pass score which is around 26 out of 40 must be correct.

Schedule can be done on any day based on what type you are scheduling, first make the payment for example in ISQI make a payment and get a code, you will receive an email and by suing the steps in the mail search for the center where u choose to write and schedule and use the code to confirm the date and time and schedule the exam!

SYLLABUS:

Chapter-1 -Fundamentals of Testing

Chapter 2 – testing throughout the Software Development Life Cycle

Chapter 3 – Static Testing

Chapter 4 – Test techniques used

Chapter 5- Test Management (Entry/Exit criteria etc..)

Chapter 6 -Tool Support for testing