Hi there guys,
Stef here and I wanted to bring you a short sharp guide on what you could do to help us blast the bug's.So we realize we have a few........ bugs within our systems and we need help to find em fix em and give you guys what you deserve.
So internally we use this form but you don't have to use this (though I would love you if you did)
The key things to remember when reporting a bug to us is to be clear concise and to try and keep away from general commentary,flavor text or guessing things. The key things we need if you don't want to use this form are :-
Is it repeatable? and exact steps you took for something to break.
One of the hardest things in development is fixing something that is not broken on our end as we cant narrow down the problem and test any fix.This is why exact steps taken to break something is important.
Actual behavior vs expected behavior.
This is another key thing to make sure we are looking in exactly the right place at exactly the right broken feature e.g. "someone says when signing up to my network they get redirected to the wrong place"
vs
product
Dashboard.tm
Actual behavior
When language is changed on the sign up form I am redirected away from the sub network I am trying to join and to freedom network sign up.
Expected behavior
When language is changed on the sign up form page should be reloaded in the selected language.
So with this info we have isolated that Its a language change issue,A redirect issue, The redirect is send to freedom and is an issue on the sub networks sign up form.
The expected behavior is in case a Dev that worked on this has left us or is busy so it is given to a Dev that has not worked on the system.This will allow him to see exactly what we want it to do.
vs
"someone says when signing up to my network they get redirected to the wrong place"
So from this I get when someone is on some part of the sign up process the form is redirecting.Its not very specific and the form is made up of a lot of code so without specific details it makes it very hard to track down a problem.
So I hope this makes seance guys any questions let me know.
and in the words of Johnny Rico
So this was a bit longer than I hoped but hopefully you guys will like it and help us out.
Stef
Stef here and I wanted to bring you a short sharp guide on what you could do to help us blast the bug's.So we realize we have a few........ bugs within our systems and we need help to find em fix em and give you guys what you deserve.
So internally we use this form but you don't have to use this (though I would love you if you did)
Code:
Product
Dashboard
Beat
Etc
Etc
Bug Description
A concise description of what the problem is. Pure description, no narrative or conversational language.
Steps to Reproduce
Step by step instructions on how to reproduce this bug.
Do not assume anything, the more detailed your list of instructions, the easier it is for the developer to track down the problem!
Actual Behavior
Type what happens when you follow the instructions. This is the manifestation of the bug.
Expected Behavior
Type what you expected to happen when you followed the instructions. This is important, because you may have misunderstood something or missed a step, and knowing what you expected to see will help the developer recognize that.
Troubleshooting/Testing Steps Attempted
Describe anything you did to try to fix it on your own.
Workaround
If you found a way to make the program work in spite of the bug, describe how you did it here.The key things to remember when reporting a bug to us is to be clear concise and to try and keep away from general commentary,flavor text or guessing things. The key things we need if you don't want to use this form are :-
Is it repeatable? and exact steps you took for something to break.
One of the hardest things in development is fixing something that is not broken on our end as we cant narrow down the problem and test any fix.This is why exact steps taken to break something is important.
Actual behavior vs expected behavior.
This is another key thing to make sure we are looking in exactly the right place at exactly the right broken feature e.g. "someone says when signing up to my network they get redirected to the wrong place"
vs
product
Dashboard.tm
Actual behavior
When language is changed on the sign up form I am redirected away from the sub network I am trying to join and to freedom network sign up.
Expected behavior
When language is changed on the sign up form page should be reloaded in the selected language.
So with this info we have isolated that Its a language change issue,A redirect issue, The redirect is send to freedom and is an issue on the sub networks sign up form.
The expected behavior is in case a Dev that worked on this has left us or is busy so it is given to a Dev that has not worked on the system.This will allow him to see exactly what we want it to do.
vs
"someone says when signing up to my network they get redirected to the wrong place"
So from this I get when someone is on some part of the sign up process the form is redirecting.Its not very specific and the form is made up of a lot of code so without specific details it makes it very hard to track down a problem.
So I hope this makes seance guys any questions let me know.
and in the words of Johnny Rico
So this was a bit longer than I hoped but hopefully you guys will like it and help us out.
Stef
