RedJocker
commented
2 years ago Hi Marcell I have reviewed your comments on reports and added some comments as well.
It looks like the third tester that was assigned has bailed, so we will take a new tester to finish the testing phase.
But we can already work on the issues found by the other two reports. So first I think you should get the current version from stepik since there where changes already and update here to match that. Don't forget to keep a branch with the current state, it may be useful if you decide to revert some of the changes later on. Then open issues on the issues you intent to fix based on reports and the comments we added.
Besides test reports there is already comments on project stages and posted solutions, since the project is already published on beta, you may be interested on seeing those too.
Marcell-Juhasz
Hey marcell, how is it going?
Alexandra has told me you had some questions about test reports and fixing the project.
first thing I think you should do is comment the reports, the problem is that reporters have not shared it with permission to comment as they should have, but I have asked Ale to fix that so you should soon be able to comment on the report. The main comments intention is to make marks on points of interest for fixing, it helps keeping track of things. You can also make marks of things related to topics team to give warnings for the topics team on where to look. For an example look at this other project report https://docs.google.com/document/d/1qEh480dFMWYLQI7PWYAlFRaEnNMv0BwvnUBw06usLWU/edit#heading=h.nati7fj400rp
second thing, for a while there was a mixup and my manager though I was assigned to do the fixing and there was one issue that really had to be fixed during tests so that testers could complete the test. It was an issue with the AlertDialog, there are two versions possible to import, but only one works, I did some changes on the internal that were to improve error messages, but them the upload had problems and I had to fix the fix. Also some other fixes were made, mostly to description.
Can you already download the project from stepik? have you received the document that explain that? I think you should download the current version and commit it here. Also duplicating this branch to save this pre-test version is probably a good thing to do.
I really recommend you opening issues on the things you want to work on, that is a good driver for this kind of work. I have marked this project to watch so I think I'll be notified already, but tag me to make sure I see it.
Also another question, can you see submissions? because that helps me a lot to fix projects. We can really see what kind of failures, if error messages are enough to figure that out or if there is need to look much closer, how are tester testing (most go on a as fast as they can complete the project, which I think is the wrong frame of mind for a tester job, they should be trying to find the most bugs as they can, that is what I used to do), where they are struggling and if the struggle is their fault (most probably isn't keep that on mind, description should be clear enough as to avoid confusion and/or misinterpretations). This job is much like an investigative job, you have to take a look for the cues and interpret things, figure out error messages and user struggles.