[FAS3] - Test Suite

[skrzepto]

Focus of this testsuite is on functional testing.

Current output 25 passed, 5 skipped in 6.45 seconds

The skipped tests are current bugs in the program that need to be fixed.

Current Limitations

• Only a local postgres db is used with user postgres db named fas
  • Be able to pass parameters via testsuite to use faitout, sqlite, local pgsql, etc...
• ....

---

Squashed commits

• when generating fake data need to delete foreign key relations first
• fixing base test class to reuse db connection and reset the testapp from pyramid
• there are 5 total people in testsuite
• need to delete activity log to delete people first
• removing html string comparison as its not a very good test
• fixing string comparison
• removing unecessary code, removing trailing space
• adding pending account notification when loging in
• removed utc info from date having issues with time aware dates, hardcoded the status since sqlalchemy complains about it not being valid and not spitting out an int
• updating count for dump since it returns total of active users instead.
• url of the resource is now full path, split up string to make tests pass
• updating string comparison test to pass
• adding packages to install for test suite
• issue with registering an account now, skip tests for now so test suite can be reviewed
• This was causing a datetime comparison crash, need to investigate if this is important
• adding notes on setup up pgsql

[skrzepto]

I have the test suite run in Vagrant in a separate table. It seems to be the cleanest solution to test with an actual pgsql db that doesn't require internet connection.

[skrzepto]

@laxathom @pypingou Any thoughts on the test suite?

[laxathom]

While I like the idea of having the test suite vagrand-ready, I tend to say we should also provide a way to perform it w/o it like if we need to run the test suite from a CI system, I'm not sure vagrant is supported yet in such env.

[skrzepto]

@laxathom the test suite is able to run locally but you need to create the postgres table for it and modify to the development.ini file to use pgsql. So for example how I have it so far is if in the development.ini file has a sqalchmey url use pgsql with table name fas. The test suite appends test to table database name so user needs to create fastest table database to use for the test suite. Thats the only limitation.

[laxathom]

hm...can we maybe instead use another db name with _test rather than appending word to _test to all tables?

[skrzepto]

@laxathom just noticed i used the wrong name. I meant database instead of table. Hopefully that clears somethings up