1
I am in the process of converting a system in Delphi to C# using the SCRUM methodology, until then there is no documentation of this system.
So I would like to know what they indicate, I don’t need a very technical documentation like diagrams and etc. My major concern is to pass the system to test team without knowing what you will have to test.
Any idea, suggestion, example?
1
Where I work also have a system in Delphi that is constantly migrating to .NET. They do not use SCRUM but have the same situation of having the testing area to validate these migrations.
What they do here is to have a team responsible for drafting Test Plans so that the test team has a "script" of the entire flow to test the implementation that is released. Basically a step by step of what the guy needs to test and what the system needs to do.
I don’t know if it’s the best way but it’s what they use here.
It is a good @Vitor Ferreira, but the company where I work not a responsible team to prepare the test plans, IE, goes from direct development to testing. In case the developers themselves would have this task. Thank you for the suggestion!
Browser other questions tagged c# delphi testing documentation scrum
You are not signed in. Login or sign up in order to post.
Sit and cry..
– Maniero
"Without knowing what you will have to test"? Really? What is the reason to test then? Another thing: you will do documentation (whatever) because it is necessary for you (clearly), or just because someone told you that it is necessary? Code conversion doesn’t usually require the same level of documentation as an ongoing project from scratch. Something is wrong on a deeper level there. I will vote to suspend because today the question seems merely to ask for general opinions.. :)
– Luiz Vieira
My dear @Luizvieira, when he said "without knowing what to test", I meant that, we will convert the system and they will have to "imagine" what to test, they will have no script and much less test scenarios. The reason for testing is to ensure that the system "works" at least the way it was before.
– Marcos Vinicius
Yeah, I got it, Marcos. But I believe that if you leave it to the testers to "imagine" what to test, there are many chances that the tests will not be complete enough and miss important things. In any case, I have the impression that this is not the central point of your doubt. Still, anything anyone tells you can be valid, and the question is simply too wide. This site is not a forum. (If not yet, please read [help] and mainly [Ask]).
– Luiz Vieira
Because I am working with SCRUM and it is an agile methodology, I as a developer can not extend myself elaborating diagrams or even a test plan. What I would like to know if there is any other kind of documentation, or my exit would be a common description without following protocols(another documentation methodology).
– Marcos Vinicius
@Marcosvinicius If you are using SCRUM then you should already have user stories in your sprint, and each story has the accepted criteria (which are usually the ones that testers should test) and one of the reasons there is documentation, is to tell who will create the functionality, how it should be, and what it should expect from input and what to provide from output. This posthumous documentation generates little value, so imagine that the documentation is what it will take to solve the story
– Caputo