Talk:Boundary-value analysis

message: This article suggests the common example of using three test cases at a boundary.
I have some problems with this, as there is disagreement as to how many cases are actually useful. Beizer in Black-Box Testing gives a very strong (to me) argument that only two cases are needed, including going through the eight failure cases for a one dimensional boundary, and comparing whether three cases is better than two.
I am loathe to just change this article so as to use only two test cases per boundary, as I understand that many people don't like this reasoning. I was considering adding a new section, titled something along the lines of 'Alternate Approach'. To me that smacks of turning the page itself into a discussion (where I am assuming that this page is useful to someone who wants to know what BVA is, and see an example we don't necessarily need to drag them into a discussion). However I am more loathe to leave the article as is (I think Beizer has a very good point here, and it just seems wrong to ignore it).
Any comments? I'll check back and see what you all think.
Jtowler 18:40, 26 November 2006 (UTC)
replies: text: This is where white box and grey box comes into play. Your example is for if month (<=12) However, you don't know if the code doesn't have a special case for 12. I generally agree with your point. --Walter Görlitz (talk) 21:18, 16 May 2011 (UTC)
thread_title: Number of cases

message: I'm not sure the recent rename was correct. Is BVA a proper noun? If not WP:TITLE says it should be changed back. --Salix alba (talk) 12:25, 28 January 2007 (UTC)
replies: text: Of course it's not a proper noun. I've requested a page move 86.152.203.212 13:33, 22 April 2007 (UTC)
thread_title:  Boundary value analysis or Boundary Value Analysis 

message: Andreas - you seem to keep adding a link to an external site that contains no information about BVA. I keep removing it. Obviously this is silly. Could you add some info here why the external site you link to is relevant to an article on BVA (rather than to software testing in general). Maybe I am missing something? Jtowler 11:30, 4 December 2007 (UTC)
thread_title:  Andreas Kaufman, external link 

message: The page currently uses "you" a lot, as if it is talking to the reader.  This needs to be recast to avoid this.  --ΨΦorg (talk) 17:10, 9 June 2008 (UTC)
thread_title:  Grammatical update needed 

message: A test need to be alaways tested against a BVA so as to determine the effectiveness of the coverage. Might be imp area s gets mis...but alwasys prefr a strong planning in the context of BVa. It requies a wide arae knowledge so as to cover the mximum coverage.
regards,--131.107.0.73 (talk) 11:24, 3 November 2008 (UTC)
thread_title:  Test case scenario 

message: How does boundary value analysis compare with other testing methods (i.e. fuzz, all-pairs, etc.) in terms of the cost/benefit ratio?
--Stevepalmateer (talk) 18:56, 23 April 2009 (UTC)
thread_title:  Cost/Benefit Ratio 

message: The first sentence contains "Boundary value analysis is a software testing(Black Box) technique".
Is this limitation there for a reason?
Even if most times the requirements are used to create partitions, I think it's just as valid to use implementation details to create different (more fine-grained) partitions in order to test other code paths as well. I would remove the "(Black Box)" part from the first sentence. 194.105.120.70 (talk) 12:45, 10 January 2013 (UTC)
replies: text: True. feel free to make the change. --Walter Görlitz (talk) 15:14, 10 January 2013 (UTC)
thread_title:  Why is boundary value analysis being limited to black box testing?