Tag Info

New answers tagged

1

Building the QA department from scratch is in a sense a great opportunity, as you don't have the old practices to get rid of, but then again you probably need to stress the the importance of the QA to others to get the support your departments will need. So for centralizing stuff, you will probably want to pick a solution that support requirements, manual- ...


0

I would consider 3 parameters to decide on partitioning: Position Size and Input With respect to Position, I would create 2 partitions: Alphabetic character at 1st position, with rest as a valid condition (i.e size between 4 to 40, valid set of input). Non-Alphabetic character at 1st position, with rest as a valid condition (i.e size between 4 ...


0

I would test: Negative tests LT 4 chars GT 40 chars GT 3 chars with non-alpha in pos 1 Non allowable special character in pos 2 - 40 (1 test, not all positions) Positive Tests GT 3 chars with lower case alpha in pos 1 GT 3 chars with upper case alpha in pos 1 Mark Smith.


0

First, you don't need to test conditions defined by partitions 4-8 on groups defined by partitions 1 and 2. These groups of input strings fail a requirement, and are therefore invalid. "Fail fast, fail often!" Next, you have another "sink-or-swin" requirement that can cut your testing in half. Literally. Either the first character is a valid alphabetical ...


0

The three basic partitions look good if you use an alphabetic character in the first position and valid characters everywhere else. Next partition would be a valid length with valid characters but starting with a non-alphabetic character. Last partition would be a valid length with an alphabetic character in the first position and at least one illegal ...


1

Though you specifically say you want separation of responsibilities I'll go ahead and recommend to you InformUp which is a full-featured ALM with requirements management, test case management, bug tracking and built-in wiki. By the way, as an ex-Microsoft stack person you say you are, you'll be right at home with InformUp's IIS based stack. If you really ...


0

Consider TRAC. It free/open source integrated wiki for documentation, bug tracker, subversion/Git/mercurial/... code repository, and code viewer. Code viewer is smart enough to parse comments in code and correctly interpret them as hyperlinks to docs or bug tracker. Comments in bug tracker can expands to changeset, etc. Atlassian wiki (confluence) is very ...


1

My thoughts were mainly keeping projects separated for issue tracking (not sure of the software we will use yet). I am a fan of Atlasssian's products. You can get issue tracking with JIRA, documentation with Confluence, communicate with HipChat, and host source code on BitBucket. Where I work now, uses these. I came from a .Net stack that used TFS and ...



Top 50 recent answers are included