True BDD implementation in SDLC

113 views
Skip to first unread message

shubhakiran b.s

unread,
Apr 24, 2020, 5:48:17 PM4/24/20
to cu...@googlegroups.com
Hi All,

Can someone explain if true BDD has to be implemented rather than just testers using BDD as tool for testers. 
1. What is best practices to have BDD for front end and Back end in SDLC ?
2. What types of testing would be covered as part of SDLC ?
3. Do we use BDD for End to End Testing? 
4. The role of QA in the overall BDD implementation, can you elobrate? 

Thanks 
SK

Hector Fontanez

unread,
Apr 24, 2020, 11:22:10 PM4/24/20
to Cukes
In my opinion, yes it has. In fact, I don't think that BDD is all that new of a concept.  If you think of what Waterfall is, it is a development process that is business driven.  I will try to answer your questions the best way I can.

1) I will let you research that. That might be a bit subjective and too lengthy to get into.

2) All types of testing should be covered as part of your SDLC; starting with the most neglected of all: Unit-level testing. I like to use pyramid to illustrate the amount of testing that needs to be done. At the lowest of levels (code) you should have way more tests than at the next higher level (integration), and so on. Your UAT and other E2E should be way less. For starters, it costs more to develop, maintain those tests, and to run. It is also harder to debug a system by running E2E. Trust me, I have been down that road many times and it is not pretty. In fact, if you feel you need to cut corners, don't do it a the unit level, do it a the top.

3) Yes. If you are developing software, you need to make sure your tests traces back to the contract. If you developing software for the entire world to use, with more of a reason you need well constructed use cases that you can use to derive your tests from. Otherwise, how can you be sure that what you're building satisfies the needs or your users?

4) Advisor? Code Police? I have been in teams where QA is totally neglected and not asked to be involved in development. The result is almost always the same: bad decisions that makes it harder for QA to test. Then QAs are ask to deliver under stress with almost impossible deadlines.Think about this, user-friendliness and performance are almost always in conflict with each other, but are both important. Likewise, QA serves as a balance to DEV. While developers focus on how to implement something, QA counters with how to make that testable. Compromises need to made early on, and QAs are not involved, only one side will be considered.

aslak hellesoy

unread,
Apr 26, 2020, 10:09:42 AM4/26/20
to cu...@googlegroups.com
On Fri, 24 Apr 2020 at 22:48, shubhakiran b.s <sukr...@gmail.com> wrote:
Hi All,

Can someone explain if true BDD has to be implemented rather than just testers using BDD as tool for testers. 
1. What is best practices to have BDD for front end and Back end in SDLC ?


I explain this in detail here:


2. What types of testing would be covered as part of SDLC ?

It depends on your context. I can’t give general advice here.


3. Do we use BDD for End to End Testing?

BDD is development, not testing. I recently wrote about this here:

And talked about it here:


 
4. The role of QA in the overall BDD implementation, can you elobrate? 


Discovery and Formulation. BDD done well (by developers) usually leads to fewer defects. QA automation efforts can be reduced to exploratory testing.

And of course other kinds of testing that BDD doesn’t replace, such as performance, security and usability testing.


Thanks 
SK

--
Posting rules: https://cucumber.io/support/posting-rules
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cukes/CAB9uRAXnUjnf7pXrCuoGMX1cazLyL9Va5H0FxbMcw%2BXZjwdLbg%40mail.gmail.com.

shubhakiran b.s

unread,
Apr 26, 2020, 3:56:49 PM4/26/20
to cu...@googlegroups.com
Thanks Aslak. It was helpful. 

I totally agree BDD is testing tool. 

Is there a way or in your experience what is best reusability that can be made from developers code to be utilised by testers to build the End to end test. Or would to recommend testers to have end to end test built separately.

Thanks in advance.

Regards,
SK

Aslak Hellesøy

unread,
Apr 27, 2020, 6:41:17 AM4/27/20
to Cukes


On Sunday, April 26, 2020 at 8:56:49 PM UTC+1, sukruz013gmail.com wrote:
Thanks Aslak. It was helpful. 

I totally agree BDD is testing tool. 


I didn't say that. I'm not sure if this is a typo or if we have a misunderstanding.

BDD is not a tool, it's a process. Simply put, the process is to write tests first, then developers use feedback from the failing test to write production code.

The BDD process is *not* a testing process. It's a *development* process.
 
Is there a way or in your experience what is best reusability that can be made from developers code to be utilised by testers to build the End to end test. Or would to recommend testers to have end to end test built separately.

If the developers have done their job well you already have a test suite that gives you confidence.
If not, I'd recommend you build this separately, or work with the developers to build it together.

Cheers,
Aslak

To unsubscribe from this group and stop receiving emails from it, send an email to cukes+unsubscribe@googlegroups.com.

--
Posting rules: https://cucumber.io/support/posting-rules
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+unsubscribe@googlegroups.com.

shubhakiran b.s

unread,
Apr 27, 2020, 7:30:56 AM4/27/20
to cu...@googlegroups.com
Apologies. That was for sure a typo error. 

To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.

--
Posting rules: https://cucumber.io/support/posting-rules
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.

--
Posting rules: https://cucumber.io/support/posting-rules
---
You received this message because you are subscribed to the Google Groups "Cukes" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cukes+un...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/cukes/172edb1c-a1b2-4b49-9911-096115358b0b%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages