The /seed option value is not being used to generate tests

Bug #1212890 reported by Charlie Poole
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
NUnitLite
Fix Released
Medium
Charlie Poole

Bug Description

Make two runs specifying the same /seed command line option, saving the results to two different XML files. The correct initial seed value is shown for both runs but the generated test cases do not replicate the same sequence of seed values as they should.

If this can't be fixed for the 1.0 release, then the /seed option should be removed
until it is made to work correctly.

Related branches

Changed in nunitlite:
status: New → Triaged
importance: Undecided → Medium
description: updated
Changed in nunitlite:
milestone: none → 1.0
assignee: nobody → Charlie Poole (charlie.poole)
Changed in nunitlite:
status: Triaged → Fix Committed
Changed in nunitlite:
milestone: 1.0 → 1.0b2
Changed in nunitlite:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.