New answers tagged qa-developer
I agree with the others, anyone should be able to enter bugs. One comment on: Especially if they are not well described with steps to reproduce? If the bugs being entered are not productive, I would invest some time those people to train them in the art of great bug writing. You just might make a great tester in the end.
Some thoughts here: how healthy is the situation where bugs are logged by project members other than the actual qa member who is the dedicated personnel for quality? This is normal - anyone can log a bug. The team decides which bugs are in scope for the project and which need to go into the main backlog. The team decides which bugs get fixed when ...
Anyone who has access to the application should be able to file bugs/defects. Defects should be filed in a bug tracker with a status new. New defects should be verified and extended (With at-least a reproduction path) Defect should be added at the top of the backlog (Keep a no defect policy when being Agile) Products Owners should monitor new incoming ...
I tend to prefer allowing anyone in any capacity to log defects on any team I am a part of. It helps build a sense of ownership of quality in the entire team, which is as it should be, every team member regardless of role should equally own and care about quality. It is a different story when people outside of the project team are entering defects, I would ...
What helped me familiarize with the application on which I'm working, was having a local repository of the application, and i ran it locally on my machine. So when I needed to know something about validations or conditions I would just debug or look at the code. This might not be the fastest way to learn the app but eventually you will. You can also ask for ...
There's no one true way to do this, but there are some common things you can do to get an overview of the system you're working with. My approach is to start with a series of questions (not in any particular order) Who - who is the application intended for? Knowing who the users are tells you a lot about how they're likely to want to use the software and ...
Know your use cases, your SW test engineer is right in that. As soon as you know what the application does, you can identify and focus on the relevant snipets of HTML/JS (I guess so from your mention of selenium).
I suggest you to use UIAutomator framewrok, it's a very simple tool to write tests for android app. UIAutomator framework has been created by Google. You should be fimilar with Java. And yes, you must learn app manually at first.
Top 50 recent answers are included