As a qa company we recommend that Reports are the best way to showcase all the efforts that being a QA Team we put in.
So in order to make the stake holders happy, we recommend to do design a Format and share Weekly, Bi-Weekly or Monthly reports for all the team. With this all will be in sync of the accomplishments those have been achieved and what's ...
Some possible conflicts that might arise between BDD and SAFE that come to my mind are
SAFe tries to sync work between multiple teams and that could make the approach less agile
It is also possible teams are sharing members so there could be less time for the Three Amigos meetings and all the conversations that are the essential part of BDD.
One set of tests
You've clearly defined a common problem that many of us face.
I have tried all of the solutions you outlined but they all seem to run into the issue of a lot of maintenance and knowledge and updating code based on environment.
My recommendation is one set of tests. If there are dependencies, e.g. database you create a connection ...
What usually works best for me, mainly in small test teams with tight schedules, is developing test automation and manual testing together.
You start by testing exploratory in a not-very-scripted way as a way to learn the product, as you go you start taking notes and build a more scripted approach (or at least more organized).
At the same time you start ...
There is no specific rule for it, as the eventual decision (manual test first or automation script) boils down to the situation. As a guideline for software testing services, one can say that for a newly feature, the manual tests comes first, even before the development happens. This is in accordance with TDD. These tests usually act as metric for the ...
This is a common question in a qa company. For that purpose, you need to have the metrics that covers the following:-
Number of delivered defects/test execution per team member vs number
of delivered features per team member
Number of business days on
average that a feature is in the process as well as in a stage
With these metrics, you can always know:
In testign everything is context depended . Its hard to suggest merits and demerits unless you states the following things like :
What methodology you work in (Agile or waterfall ?)
What is your sprint length
How much time you gets for testing
What is your responsibility ( Is it only manual , is it automation or is it both)
What is the Team size
What is the ...
There's no one answer to this. It's highly dependent on the context in which you are working.
For example, I've worked in fields with varying degrees of regulation, where traceability from requirement and change through test case execution is vital. In these cases, having a test case documented in a test case management tool and selecting appropriate test ...
I test a web-based product and am good at exploratory testing, scenario testing, do proper analysis, know database SQL queries and try my best to find critical problems in functionality, but don't use programming or tools.
I wonder how you access a database without tools... I think you already use a lot of tools, bez perhaps you are not aware of that.
Do I ...
'if I dislike coding and don't understand complex code, then will I be able to survive as a QA':
Answer: Yes. Areas such as ACCESSIBILITY TESTING do not need automation exposure at all. At the same time, each country has brought accessibility rules and regulations to their Acts hence accessibility engineer is a growing role for manual tester in recent times.
If you’re looking for a cloud-based ecosystem, you can try LambdaTest - a cross-browser testing tool. It avoids the need to maintain an in-house architecture by offering a flexible online testing cloud.
LambdaTest provides you with an online Selenium Grid that enables you to run both manual and automated software tests of your websites and web apps over 2,...