Welcome to SQA, Rosa. I am not sure your question makes sense; QA is an abbreviation for "Quality Assurance", and often is used as a synonym for testing. ISTQB is a type of certification for testers.
See also Do ISTQB/ISEB Testing Certificates prove that someone can test? and http://en.wikipedia.org/wiki/Caps_lock.
This question is bogus. As the most expensive fix depends on the complexity of the fault. Small issues in any stage of the software development cycle are cheap to fix. As complex issues might need a complete rewrite. This rewrite might not be caused by wrong requirements, but by spaghetti-code or the other way around, depending who and where took the ...
There are many ways to expend the knowledge as a QA:
Read QA blogs.
Read Testing books.
Hone your QA skills by teaching others.
Go to Meet-Up & grow your network.
Search & Read the Research Papers.
Go to the Conference & Company Seminar.
One of the best ways to learn Ask Q/A on Stack Exchange sites.
Work on Open Source /Crowd Testing Projects. (...
No, absolutely. The problem with ISTQB Syllabus is that it does not really reflect modern approaches and methodologies (especially in agile environments). I attended ISTQB training recently myself and I must say that at least half of it was useless (problems that were mentioned do not exist in an agile team to which I belong).
Although it does not ...
Alpha Testing is mostly done in-front of the developers by the product owner or the customer, to let developer notice where the user can be go wrong with UX and etc, from the users perspective before releasing a solution.
Beta Testing is basically releasing the solution to the consumers to use and report the bugs and enhancements, where then the developers ...
Here is a state diagram and its corresponding state table:
It is pretty much self-explanatory now.
'E' from state 'S2' is valid
'E' from state 'S3' is invalid
Now, the problem with your question is the table format. There is no way to guess what comes under 'F'. Also, under 'A', there are too many parameters even if we move out the first column.
Technical Test Analyst most closely aligns with "Test Engineer" whereas the Test Analyst is just a tester.
Engineer or Technical implies the knowledge and capability to do more than just stay on the surface but to be able to dig around into the engineering makeup of an application or product. If you were doing some oil rig testing, you would want an ...
I think the differences are best explained by comparing their skill sets:
From my personal experience:
Technical test analyst is involved with more test automation.
Test analyst is involved with more business UAT.
The borderline between them is not strictly black-white, most of the time, it is merely a title. It does not mean a test analyst can not do ...
Chow's switch coverage describes how you cover a state transition model. A "switch" in this context is a state in between your beginning state and your end state in your traversal of the model. So 0-switch coverage means that you exercise every direct transition possible in the model. 1-switch coverage means you allow one state between your start and end ...
Is there anything wrong with my flowchart?
Yes and no. It is correct functionally: it describes exactly what the code is supposed to do. However, in code, Display_messageZ is called in two places (instead of one, as in your chart).
Why is my answer incorrect?
Because you follow the chart instead of the code, you miss the second call to Display_messageZ to ...
The correct answer seems to be C.
Keep in mind though, that not all of these online questions are actual ISTQB exams questions, and even if they are, answers are not always correct (as you can see).
A more relevant (and more likely to occur) question would be this:
When should you stop testing?
when time for testing has run out.
when all planned tests ...
The official site for downloading syllabus and materials:
Additional links to go thro:
Test open source software and report defects on Github. Maybe start with the top open source applications, you might already be using some.
Try to answers questions here on SQA.SE. If you cannot answer them do research (and create a proof of concept) until you can. This helped me greatly.
Read testing blogs
Read testing books
My personal opinion is that ...
I've read "Foundations of Software Testing: ISTQB Certification" by Dorothy Graham et al. For each chapter of Syllabus it has sample example questions, together with correct answers and reference to the paragraph explaining why it is correct.
On ISTQB site there is is also a free sample of exam questions and correct answers but without explanation why it is ...
In my experience the google answer reflects the common understanding, while the ISTQB syllabus takes on a more theoretical approach. I will elaborate the ISTQB view from my understaning here:
The focus of these tests, in genereal, is to simulate user / customer behaviour(hence the "potential"). You are conducting these as parts of the acceptance tests.
Googling this question gives multiple sites where there are some example questions or mock tests for preparing for ISTQB foundation level certification.
They illustrate well one of the problems in this kind of certification. None of the sites I found explained why this would be the correct answer (or asked for the applicant to explain it, for that matter). ...
BVA and unit tests
It depends on when and how the developer implements the unit test. If the developer writes the test first (as recommended by test driven development, TDD), it's a black box test, because he doesn't see the implementation. In that case, the test conditions can only be based on the software specification.
If the developer writes a unit ...
I have taken this exam and in first attempt I scored 92.5% marks, so its not a very difficult exam. You just need to download the syllabus from ISTQB website and study all the topics for around 1 month. No need to study anything from outside. The syllabus is enough.
When you will appear in the exam you will find that almost all the questions you have read ...
A number of answers can be figured out through the process of elimination - even ones that don't necessarily make sense to you.
In the example question, you can knock out 2 and 3 straight away... we know they're false, which also means the answer can't be A or D.
We can also take out 4 because an incident should include information on test environments (...
The level of difficulty depends on how much you already know before seating for an exam.
Have a go and if you don't pass, don't be upset, review again and try again.
A combination of experience plus revision is a good start.
Review as much as you can and while reviewing, do mockup exams, there are tonnes of it online.
While I was studying I was taking ...
If the objective of the test is to only test two states this could lead to the appropriate testing technique, since it limits the technique's that are useful.
To quote from the Professional Testers Manifesto:
That testing benefits from diversity and not homogeneity: that testing
is not a profession that can be standardized but instead needs to
I assume you are currently a University student? Have you checked in with your advisors and/or the placement office at your school? I wonder what kind of advice schools are offering these days, and if they are capable of guiding you...
Have you considered transferring into an IT program? That's very often a good way of gaining a useful background that ...
"The Objective of the test" is the answer.
As your objective will decide what you want to achieve from the Test. And by foreseeing your end result, you decide which technique you want to use.
For example, At different stages of software development cycle(or test cycle) you choose different technique to perform the test. You can't decide the technique by "...
The point this question is trying to make is:
we should build in "quality" instead of testing it out.
testing should start as soon as development starts.
if we leave any faults in earlier stages of development, they will cause "butterfly effect" and become difficult and expensive to fix. The analogy I want to use here is: earlier development is like ...
Ofcourse the correct answer should be:
Everyone who may eventually have some use for the tool
If I would have a company and I would have evaluated and paid for a tool. Then I would not want to hold people back in using it when they want to use it.
Employee: Can I use the new bought tool?
Test Manager: No, no, first the small team has to use it and ...
It's three paths. If I express it via a more c# syntax you get this:
statement = statement1;
statement = statement2;
That gives us 2 paths:
condition1 == true -> statement1
condition1 == false -> statement2
Next, statement 2 is checked for true/false:
statement = statement3
So your ...