[NCBC-203] Restructure .NET tests Created: 10/Dec/12  Updated: 14/Jan/13  Resolved: 25/Dec/12

Status: Resolved
Project: Couchbase .NET client library
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Major
Reporter: Mark Nunberg Assignee: Saakshi Manocha
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Zip Archive couchbase.tests.changedfiles.zip     Zip Archive Couchbase.Tests.zip    
Issue Links:
depends on NCBC-177 Consolidate test options from App.config Resolved

Eliminate redundant tests. I see there are some repetitive tests which differ only by 1-2 parameters. For example, we don't need individual functions for each scenario of observe, and it should be possible to abstract this all into a single function, with different tests just calling into that function with different parameters.

I recall that you brought this up as a concern before; now it's a task :)

Comment by Saakshi Manocha [ 11/Dec/12 ]
Comment by Mark Nunberg [ 11/Dec/12 ]
I've sectioned out the previous bug into an NCBC issue. In general any changes to the SDKs themselves should be branched out into issues which touch those specific projects, with the SDKQE task tracking them.
Comment by Saakshi Manocha [ 18/Dec/12 ]
updated files attached for review :
Comment by Saakshi Manocha [ 19/Dec/12 ]
please review:
Comment by Saakshi Manocha [ 25/Dec/12 ]
Mark to review the changes updated in Gerrit
Comment by Saakshi Manocha [ 14/Jan/13 ]
moved this task from SDKQE project to NCBC, as per mail from Matt so that we can use NCBC in comment while submitting code in gerrit.
updated comment in gerrit and submitted a new patch set.,
please review http://review.couchbase.org/#/c/23604/
Comment by Matt Ingenthron [ 14/Jan/13 ]
Saakshi: it's not so much that this task needed to be moved, but an underlying NCBC enhancement issue needed to be created-- even one with just a one line summary of what's to be done.

NCBC tracks this product/project, so we should always be able to see the changes in a version via this issue tracker and cross reference that with the code changes.

Generated at Thu Dec 18 08:38:36 CST 2014 using JIRA 5.2.4#845-sha1:c9f4cc41abe72fb236945343a1f485c2c844dac9.