Given the following overarching purpose (mission statement) for an application:

In order to help keep a healthy and refreshing sleep regime, or in order to limit computer-related addictive behaviours, computer users can automatically lock their devices for certain befitting times in a tamper-proof manner.

Would creating a Gherkin feature or scenario for the user request below (and later implementing it to pass) be unfitting and bloating the app or does this request actually fit under the scope of this app somehow?

Could you please also provide the option to shut down the device on lockdown, not just lock it.

  • If it does fit then how exactly is it linked to the overall value statement?
  • are you asking for our opinion about whether the shutdown feature is implied by the mission statement? Or is this a question about BDD process?
    – user246
    Apr 21 '15 at 11:46
  • @user246 Whether the shutdown feature follows from / serves the mission statement. And therefore whether such a feature should be included if wanting to be outside-in value-driven (BDD).
    – Ray
    Apr 21 '15 at 11:57
  • 1
    I'm voting to close this question as off-topic because it is about mobile app development, not testing.
    – user246
    Apr 21 '15 at 12:01
  • @user246 how is this not about testing? it is a concrete example that helps to elucidate the process of behavior driven development, in particular, how should this case be dealt with when employing this testing framework
    – Ray
    Apr 21 '15 at 12:15
  • It is an issue that arises during testing, but there is nothing test-specific about deciding whether that shutdown requirement derives from that mission statement. So this question is not about test testing.
    – user246
    Apr 21 '15 at 13:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.