Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.java.programmer > #37855

Re: Calling deprecated methods

Show all headers | View raw

On 12/13/17 12:30 AM, Kiwi User (Kiwi User) wrote:
>> I know nothing of this sort of testing though I am curious to know how
>> you'd find the data that would generate errors when a method accepts a
>> number and handles 1, 1.5, and 2 just fine but 1.6 returns an incorrect
>> result.
>>
> Traditionally, you'd read the design specification. The one thing you MUST
NOT
> do is to look at the code while you're writing tests. You're
> trying to test that it does what the requirements say it should and not what
> the coder wrote because he may have misunderstood the spec.

One major exception to this, is that the people who write the code should
report to the testers any algorithmic breakpoints that are not implied by the
specifications. For instance, the size of the data being processed my affect
which method is used to reach the goal. The test suite needs to make sure it
exercises every case. Testing likely would test the smallest and largest, but
if there is distinct middle case, it might be missed, and tests near the break
points might be called for too.

Back to comp.lang.java.programmer | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

Re: Calling deprecated methods Richard Damon <Richard@Damon-Family.org> (Richard Damon) - 2017-12-15 22:31 +1200
  Re: Calling deprecated methods Kiwi User <martin@mydomain.invalid> (Kiwi User) - 2017-12-16 09:08 +1200
    Re: Calling deprecated methods Eric Sosman <esosman@comcast-dot-net.invalid> - 2017-12-16 16:24 -0500

csiph-web