Serdar Tumgoren wrote:
> And the more I hear from you folks, the more I start thinking that my
> confusion arose because I don't have a formal set of requirements and
> therefore have to wear multiple hats
I think a base confusion was between your app's own job (validation), on one
hand, and te
Thanks to everyone for the detailed and varied responses. They really
help get me situated in this unfamiliar world of testing.
And the more I hear from you folks, the more I start thinking that my
confusion arose because I don't have a formal set of requirements and
therefore have to wear multipl
On Tue, Nov 24, 2009 at 3:41 PM, Serdar Tumgoren wrote:
> << requirements snippet>>
>
> Root node of every XML file is PublicFiling
> Every PublicFiling node must contain at least one Filing node
> Every Filing must contain 'Type' attribute
> Every Filing must contain 'Year' attribute, etc.
> Fil
As well as the other replies, consider that you are doing "unit" testing:
http://en.wikipedia.org/wiki/Unit_test
One method is black-box testing, which is where the thing (class,
function, module) you are testing is treated as a black box, something
that takes input and returns output, and how i
Serdar Tumgoren wrote:
That's a good start. You're missing one requirement that I think needs to
be explicit. Presumably you're requiring that the XML be well-formed. This
refers to things like matching and nodes, and proper use of
quotes and escaping within strings. Most DOM parsers won
"Serdar Tumgoren" wrote
Simple enough in theory, but the problem I'm hitting is where to begin
with tests on data that is ALL over the place.
I've just spent the last 2 days in a workshop with >30 of our company's
end to end test team. These guys are professional testers, all they do
is tes
Serdar Tumgoren wrote:
> Lie and Kent,
>
> Thanks for the quick replies.
>
> I've started writing some "requirements", and combined with your
> advice, am starting to feel a bit more confident on how to approach
> this project.
>
> Below is an excerpt of my requirements -- basically what I've
> That's a good start. You're missing one requirement that I think needs to
> be explicit. Presumably you're requiring that the XML be well-formed. This
> refers to things like matching and nodes, and proper use of
> quotes and escaping within strings. Most DOM parsers won't even give you a
> I'm not really sure where you are going with this? This looks like a
> data specification, but you said the data is poorly specified and not
> under your control. So is this a specification of a data validator?
>
The short answer -- yes, these are specs for a data validator.
And I should have be
Serdar Tumgoren wrote:
Lie and Kent,
Thanks for the quick replies.
I've started writing some "requirements", and combined with your
advice, am starting to feel a bit more confident on how to approach
this project.
Below is an excerpt of my requirements -- basically what I've learned
from revie
On Tue, Nov 24, 2009 at 3:41 PM, Serdar Tumgoren wrote:
> I've started writing some "requirements", and combined with your
> advice, am starting to feel a bit more confident on how to approach
> this project.
>
> Below is an excerpt of my requirements -- basically what I've learned
> from reviewi
Lie and Kent,
Thanks for the quick replies.
I've started writing some "requirements", and combined with your
advice, am starting to feel a bit more confident on how to approach
this project.
Below is an excerpt of my requirements -- basically what I've learned
from reviewing the raw data using E
Serdar Tumgoren wrote:
Hi everyone,
The list recently discussed the virtues of unit testing, and I was
hoping someone could offer some high-level advice and further
resources as I try to apply the TDD methodology.
TDD is different from data validation. TDD ensures program correctness.
Data val
On Tue, Nov 24, 2009 at 2:02 PM, Serdar Tumgoren wrote:
> Hi everyone,
> The list recently discussed the virtues of unit testing, and I was
> hoping someone could offer some high-level advice and further
> resources as I try to apply the TDD methodology.
>
> I'm trying to develop an application th
Hi everyone,
The list recently discussed the virtues of unit testing, and I was
hoping someone could offer some high-level advice and further
resources as I try to apply the TDD methodology.
I'm trying to develop an application that regularly downloads some
government data (in XML), parses the dat
15 matches
Mail list logo
