Test framework missing

Not sure of the benefit from that. You then have to create responses identical to what Tripletex is providing now. Might be a better way to agree with Tripletex on a more permanent test account that does not expire in 30 days as all free ones does.

Just committed the framework for testing through tripletex.test file. Very plain and narrow test so far: Just testing if the settings page is available when logged in.

Have approached Tripletex to ask for a more permanent testing interface for the automatic tests to be run.

Testing framework is now in place.
I suggest we make it an habit of adding a new test to the tripletex.test file every time we add a feature or solve an issue in this queue. This way we will continually increase the test coverage and make sure the test is up-to-date.
I suggest adding something like this:

 /**
   * Test for issue #1459802:Configurable invoice sequence start
   */
  public function testTripletexChangeInvoiceNumberStart() {
  }

Comments and suggestions are welcome