Datamapper DataMapper

Comments and changes to this ticket

• You flagged this item as spam.
  

  Martin Kihlgren April 16th, 2008 @ 10:02 AM

  There are probably slightly prettier ways of doing this - like, destroying and creating the table outside of an actual test.

• 

  Dan Kubb (dkubb) April 17th, 2008 @ 01:47 AM

  • State changed from “new” to “open”
  • Milestone cleared.

  This spec relies on the ordering of specs so later specs depend on earlier specs running. This will cause lots of small problems, but the easiest one to demonstrate is autotest -- if one of the specs fails, autotest will keep running the failing spec until it passes. If the failing spec depends on something else running first to create a very specific state, it will likely break when run more than one time.

  The general rule is that you can't depend on specs running in a specific order, and you can't depend on specs running just once. Use the before :all and before methods to setup the environment, and write each spec (it block) stand-alone, independent of anything else.

• You flagged this item as spam.
  

  Martin Kihlgren April 17th, 2008 @ 02:32 AM

  Yes, the fact that the spec relies on ordering is broken, and should be fixed. I can fix that when I have push privileges (I am getting tired of creating a gazillion tickets for small fixes :)

• 

  Martin Kihlgren April 18th, 2008 @ 03:41 AM

  • State changed from “open” to “resolved”

  Now the test is prettier, with each spec (I think, it was a fairl quick hack) running completely on its own, with before :all in each part.