9
Does it matter? Sounds like impostor syndrome. Your probably less confident about your skills than you should be, it is the Dunning-Kruger effect.
In my book, you are good enough at anything, if you accept your current skill level. Have a plan to improve. Act on your plan weekly.
answered Apr 20 '19 at 7:32
Niels van Reijmersdal
31.7k4 gold badges52 silver badges118 bronze badges
9
You could start with unit tests, while the application is being developed. In Java you can use JUnit for this.
If you don't have a fully functioning system yet, you can use mocking to mock objects. In Java this is done with Mockito or JMockit.
Look into unit testing and TDD (Test Driven Development).
Once you are ready to integrate different components, ...
9
It reads to me as though your organization is using the SM role in a somewhat different way than classic Scrum, so my suggestions could be way off-target here.
Classically, the SM role is to facilitate progress by finding ways to clear or work around any impediments that arise during a sprint, to lead meetings, to ensure that meetings stay on-topic and stay ...
5
A key area you are missing is Technical Excellence as described by the LeSS framework.
Specification by Example
Thinking about testing
Continuous integration
Continuous delivery
Architecture & design
Clean Code
Acceptance testing
Test automation
Test-Driven development
Unit-testing
These might sound like development practises and some are, still I ...
answered Jul 24 '17 at 14:07
Niels van Reijmersdal
31.7k4 gold badges52 silver badges118 bronze badges
4
How can QA honestly identify their own strengths and weaknesses?
Education and comparison
Read blogs
Read books
Teach others
Go to meetups
Go to conferences
Work at different companies
Ask and Answer on Stack Exchange sites
Do enough of the above and you should have a pretty good idea where you compare to others in those books you'll have read and in those ...
4
NDepend is the .NET equivalent of JDepend.
You can find more info about the metrics here.
3
A qa architect is a person who design the building block of qa process. Basically this is more relevent to test automation where many things comes in picture. So his role is to place and consult the optimized way to place the block so that whole system is stable economic scalable, fast and optimized. Test automation uses a lot of resources like machines. ...
3
In essence, it doesn't change much, after all...
“Testing is the process of evaluating a product by learning about it
through exploration and experimentation, which includes: questioning,
study, modeling, observation and inference, output checking, etc.” James Bach, Exploratory Testing 3.0
Therefore, the idea behind testing architectures ...
3
You are UI tester, so tools and approaches for unit testing (TDD) suggested in other answers are mostly useless for you.
I hope your developers are working in iterations (not a waterfall), so your concern of what to do while code is being developed is valid only for first iteration. After first iteration, you should have working code delivered in the ...
3
Are you asking about test driven development? This practice need not just tools, but also special steps/processes prior to writing a test or any code.
Try to look at the article and the tools list here: Introduction to Test Driven Development (TDD). Most of them are, of course, a unit testing tools. But some of them are more complex.
Also, a Wikipedia ...
3
You asked about quality, but then you asked about performance, so I assume you are specifically interested in performance. The short answer is no. There are tools that will analyze performance while it is running to tell you which parts of the code are the busiest. Those tools will not tell you whether you are using slow algorithms. And a hot spot is ...
2
It really comes down to overall reliability and speed.
If you can guarantee that you have 24/7 access to your 'test server' via the Internet, with guaranteed > 10Mbps download/upload speeds, and you can protect 100% from external attacks (e.g. DoS) then the Internet might be the way to go.
But, if you are like most of the world that experiences ...
2
It should be hosted where everyone who needs to test can access it.
Important is that everyone can test in isolation, you don't want different processes or users interfering with each others tests runs.
As you tagged this question with "continuous integration" I would like to add that for automated tests I love to spin up a test environment from scratch so ...
answered Mar 14 '14 at 20:22
Niels van Reijmersdal
31.7k4 gold badges52 silver badges118 bronze badges
2
Kate notes the classical example in her answer, it maybe you are not in that sort of environment.
I've been in companies where the desire to use an Agile/Scrum process often outstrips the personnel abilities of the company. Either you cannot hire an additional person to be the full-time SM or you can't get dedicated training. So you do need to have ...
2
Good practices for UI test automation
Technical Excellence for clean code and TDD
Write human readable tests as documentation
Keep tests DRY with helpers for repeated steps
Use a BDD approach such as Given, When, Then
Perform javascript unit testing with HTML fragments
Ensure that Happy, Sad and Optional paths are tested
Use Page Data Objects for data being ...
2
Given you use Selenium most probably your target is a web application. One of the options would be go a level down and perform your testing using HTTP Protocol, the pros are:
The tests are not that fragile as UI-based ones
CPU and memory footprints of protocol-based tests are much lower
Functional tests can easily be turned into load tests by just adding ...
2
The answer here falls into the "Yes, but..." category.
Yes, the test team can own documentation. The potential issues here include:
You will still be surprised by changing business requirements. It doesn't matter who writes the requirements documents: if what the user wants doesn't match what the requirements documents say, there will be problems.
Your ...
2
Try to proactively look for potential problems ahead of the actual testing. Several sources: Any errors which pop up in products you tested - and find out how you could have avoided it. Errors which others in your company or field missed before. Errors associated with any changes in how your company does things (new approaches in management, development...). ...
2
Many testers before have asked this question already. Here are few links (blogs & video):
Katrina Clokie - How do you become a great tester?
Christin Wiedermann - SMARTER TESTING THROUGH SMARTER TESTERS
Zeger Van Hese - The Power of Doubt – Becoming a Software Skeptic
Helena Jeret-Mäe - How to Start Learning about Testing
I cannot find the link of ...
1
I like to answers questions with questions during interviews.
My first response would be that the question "How to test AWS?" is very broad.
My first question would be: Which part of AWS should I test?
As of 2020, AWS comprises more than 175 products and services
including computing, storage, networking, database, analytics,
application services, ...
1
Every person is having some weakness and strengths. But in professional world every person want to be less prone to mistakes. For achieving this QA tester have to keep in mind below mentioned points and should try to implement in qa services:
If a mistake is repeated then QA should make a checklist of that areas and should run the same whenever testing a ...
1
First, to know whether you are a good tester or not (or you have tested a product well or not), the scale to check is the number of bug slips. If the number of bugs from the client / user end is more, and you had missed them in QA, SQA, UAT, Mock Live envs, then the number of bugs speak something isn't it?
And to understand the strength and weaknesses, both ...
1
The situation that you described will not end up good for someone or for whole team if changes in right direction don't occur in time.
Since you probably don't have the authority to change this situation but must do your job, then try to do exactly that.
I would suggest to do this things:
Create general test documentation where you will have ALL open ...
1
Very Big Project has a project manager (or few). They should decide what would be beneficial for the project as a whole.
If QA volunteers to write docs, but no one else will care about providing inputs, you just set up QA for a spectacular fail. Because only the manager can tell others what they have to do, and if QA will have responsibility but not the ...
1
The biggest problem with QA owning requirements and documentation is the loss of division of duties.
In a worst case scenario QA could then change the requirements after the software has been developed so that all tests pass. There should be a division of duties between the people who write the requirements, the people who develop software too those ...
1
If you are strictly doing UI automation limited to black box testing only, then I would recommend top to bottom approach doing BDD/ ATDD using tools like cucumber which sit on top of selenium.
Till development is complete , in parallel you may start developing feature files based on user stories, once development is complete ,or UI is available (mockups) ...
1
Consider the following areas and topics:
1
This article has a great definition of what a QA Architect is:
https://medium.com/@maomrtnz/whats-a-qa-architect-9efc98037255
Only top voted, non community-wiki answers of a minimum length are eligible