New answers tagged

1

The definition of ‘functional requirement’ is that it essentially specifies something the system should do. The definition for a non-functional requirement is that it essentially specifies how the system should behave and that it is a constraint upon the systems behaviour. One could also think of non-functional requirements as quality attributes for of a ...


0

Generally I try and create end-to-end workflows for major functionality. I group tests by file. One approach I also use is to use tags for happy, sad and options workflows. Happy is being the quick, all correct input route Sad is trying to generate as many errors as possible Options means adding other stuff. Will depend on the application and data. I ...



Top 50 recent answers are included