#1440 Integration test for repo.refresh

unreleased
wont-fix
nobody
sf-4 (350)
SCM
nobody
2011-07-01
2011-02-03
No

Add an integration test for repo.refresh

This has been failing due to a missing ini key. An integration test can prevent similar occurrences, and validate that the refresh worked.

Discussion

  • Dave Brondsema

    Dave Brondsema - 2011-02-03

    I think this can go in AlluraTesting, doesn't have to be sourceforge.net-specific

     
  • Dave Brondsema

    Dave Brondsema - 2011-02-10

    We decided to run this in the forge-classic integration tests, where mechanize is already in place and services are running.

     
  • Dave Brondsema

    Dave Brondsema - 2011-02-10
    • size: --> 2
     
  • Mark Ramm - 2011-03-22
    • size: 4 --> 4
    • milestone: mar-31 --> backlog
     
  • Dave Brondsema

    Dave Brondsema - 2011-04-07
    • status: open --> wont-fix
     
  • Dave Brondsema

    Dave Brondsema - 2011-04-07

    We haven't had issues with this again, the test won't be easy to write, and we have other mechanisms in place now to catch .ini changes

     

Log in to post a comment.