PERGUNTAS QUE RECEBI EM ENTREVISTAS

- What are the test types?

o Functional Testing
o Non- functional Testing
o White-box Testing
o Change-related Testing

- Difference between functional and non-functional testing?

Functional testing is based on customer’s requirements and verifies each
function/feature of the software whereas Non-Functional testing verifies aspects like
performance, usability, reliability, etc.
Functional describes “what the product does” whereas Non-Functional describes “how
the product work”.

- What is end-to-end testing? Give me an example?

Method that validates entire software from starting to the end along with its
integration with external interfaces. Example:
Login into the banking system -> Check for the balance amount in the account ->
Transfer some amount from your account to some other bank account -> Check your
latest account balance -> Logout of the application.

- Difference between functional and end-to-end testing?

Functional testing is limited to one single piece of code or application, ensures the
tested software meets acceptance criteria and validate the result of each test for inputs
and outputs.
End-to-End testing ensures a process continues to work after changes are made. Tests
the way multiple users work across applications, validate that each step in the process
is completed.

- When do you know that is enough testing (definition of done)?

o Planned tests have been executed
o A defined level of coverage (e.g., of requirements, user stories, acceptance
criteria) has been achieved
o The number of unresolved defects is within an agreed limit
o The number of estimated remaining defects is sufficiently low

- When do you know you can start testing (definition of ready)?

o Availability of testable requirements and user stories
o Availability of test items
o Availability of test environment
o Availability of necessary test tools
o Availability of test data and other necessary resources

- What is important, for you, to have in a test case?

Pre-conditions, Actions (steps) and Expected Results.
- How do you prioritize your test activities?
- The project has no requirements, how do you design test cases in this case?
I would use the test exploratory in the current version of the application and with this
reference design test cases.

- What are de main topics of a test plan?

o Scope and objectives of testing
o Features to be tested and not to be tested
o Approach for testing
o Pass/fail criteria and other metrics
o Testing tasks
o Testing environmental needs
o Responsibilities
o Schedule of test analysis, design, implementation, execution, and evaluation
activities
o Risks and mitigation

- Difference between test plan and test strategy?

Test Plan is a document that describes the scope, objective, and approach of testing
task, and has the primary goal of how to test, when to test and who will verify whereas
Test Strategy describes how testing needs to be done and has the primary goal of what
technique to follow and which module to check.

- Which do you perform first, smoke or regression testing?

Smoke I performed first, then regression.

- What is smoke testing?

Is a software testing technique performed post software build to verify that the critical
functionalities of software are working fine. It is executed before any detailed
functional or regression tests are executed.

- What is sanity testing?

Is a test performed after receiving a software build, to ensure that the code changes
introduced are working as expected. This testing is a checkpoint to determine
if testing for the build can proceed or not

- What are the differences between sanity and smoke testing?

Smoke Testing is performed to ascertain that the critical functionalities of the program
is working fine and Sanity Testing is done to check the new functionality/bugs have
been fixed.

- Do you know any metrics used in testing?

o Percentage of planned work done
o Number of test cases run/not run, test cases passed/failed, and/or test
conditions passed/failed)
o Defect information (e.g., defect density, defects found and fixed, failure rate,
and confirmation test results)
 o Test coverage of requirements, user stories, acceptance criteria, risks, or code

- What about metrics specific for scrum?

o Sprint burndown: It shows the number of hours remaining to complete the
stories planned for the current sprint, for each day during the sprint
o Escaped Defects: Shows how many bugs were experienced by users in
production.
o Defect Density: It measures number of defects per software size.
o Velocity: is the average amount of work a scrum team completes during a
sprint, measured in either story points or hours.
o Cumulative flow diagram

- Do you know what is lead time?

Is the time it takes for a task which appears in your workflow to be completed and
delivered to customers. (it’s used in Kanban methodology)

- What are the roles in scrum?

o Scrum Master: ensures that Scrum practices and rules are implemented and
followed, and resolves any resource issues, or other impediments that could
prevent the team from following the practices and rules.
o Product Owner: represents the customer, and generates, maintains, and
prioritizes the product backlog.
o Development Team: develop and test the product. The team is self-organized:

- What is an iteration?
Is a standard, fixed-length timebox, where the Agile Team deliver incremental value
in the form of working and tested software.

- When do you use checklist instead of test cases?

A Checklist is a list of items to be verified at the end of a sprint or release. I usually
use checklists when I need to repeat the same steps over and over, for example a
checklist to check the production environment after a release.
And the tests case I use to validate the functionalities of the system when it has been
developing.

- Difference between priority and severity?

Severity is the degree of impact that a defect has on the system; whereas,
Bug Priority is the urgency that the defect has to be fixed.

- Give a case where you have a bug with low severity and high priority
High Severity - Low Priority
This happens when the bug causes major problems, but it only happens in very rare
conditions or situations, for example, customers who use very old browsers cannot
 continue with their purchase of a product. Because the number of customers with very
old browsers is very low, it is not a high priority to fix the issue.

High Priority - Low Severity

This could happen when, for example, the logo or name of the company is not
displayed on the website. It is important to fix the issue as soon as possible, although it
may not cause a lot of damage.

- Give me a functional test scenario

Check if the field only accept numbers

- What are the test estimation techniques that you know?

The metrics-based technique: estimating the test effort based on metrics of former
similar projects, or based on typical values
The expert-based technique: estimating the test effort based on the experience of the
owners of the testing tasks or by experts

- In which environments do you usually test?

I usually test in development/testing and acceptance environment

- What are the factors that affect test estimation?

o The risks associated with the product
o Quality of the test basis
o Size of the product
o Test approach
o Test process
o Time pressure
o The number and severity of defects found and the amount of rework required.

- Case where your estimated time was two days and you will take a week to test
and you are in the middle of the sprint (of two weeks), what do you do?
If the development team cannot finish a task within a sprint, the associated product
features are removed from the sprint and the task is moved back into the product
backlog.

- In the middle of the sprint, the client wants to exclude the functionality been
developing and add a new one, what do you do in that case?
I think this is not something that I could decide, I think this is a higher up decision that
should be discuss by the scrum master, productor owner and if necessary, the
manager.
- What is the bug cycle?

- Is it mandatory to assign to the developer?

No, it’s not mandatory, in scrum the responsibility of the bug is of the whole team. So,
any person of the development team can work resolving the bug.

- You open a bug and the developer manager says that is not a defect, what do you
do (in scrum)?
I would talk to the scrum master so he can help us to resolve the issue.

- What is Continuous Integration?

Continuous Integration (CI) is a practice that requires developers to integrate all
changes made to the software regularly, at least once a day. This way the problems are
detected more quickly.

- What are the differences between continuous integration, continuous delivery

and continuous development?
Continuous integration is a development practice that requires developers to merge
their changes back to the main branch as often as possible.
Continuous delivery is an extension of continuous integration, is the continual delivery
of code to an environment once the developer feels the code is ready to ship.
Continuous deployment is the deployment or release of code to production as soon as
it’s ready.

- What factors impact automation?

- Every test case can be automated (functional testing)?
- Which tests can you automated?
- When automation is not desired?
- How do you decide what to automated/?

- Difference between SOAP and REST?

SOAP is a protocol whereas REST is an architectural pattern and SOAP only works
with XML formats whereas REST work with plain text, XML, HTML and JSON.

- What is JSON?
JSON is a syntax for storing and exchanging data. Is text, written with JavaScript
object notation.

- What is XML?
XML is a software tool (is a markup language) for storing and transporting data.

- Difference between JSON and XML?

o JSON doesn't use end tag
o JSON is shorter
o JSON is quicker to read and write
o JSON can use arrays

- Difference between XML and HTML?

o XML was designed to carry data - with focus on what data is
o HTML was designed to display data - with focus on how data looks
o XML tags are not predefined like HTML tags are

- What is the view of the database?

A database view is a searchable object in a database that is defined by a query.

- What are the types of JOIN (sql)?

o (INNER) JOIN: Returns records that have matching values in both tables
o LEFT (OUTER) JOIN: Returns all records from the left table, and the matched
records from the right table
o RIGHT (OUTER) JOIN: Returns all records from the right table, and the
matched records from the left table
o FULL (OUTER) JOIN: Returns all records when there is a match in either left
or right table

- You know what is a TRIGGER?

A trigger is a special type of stored procedure that automatically runs when an event
occurs in the database server. For example, a trigger can be invoked when a row is
inserted into a specified table or when certain table columns are being updated.
https://www.saucedemo.com/cart.html - login, get highest and lowest price and then remove
from cart