WIP: #630: Create tests for talkeditor.py following PR #605

Now that PR #605 has been merged, I would like to add some tests for the new functions I created. I will have a better idea of what steps this requires as I start experimenting, but I thought I should create this PR as soon as possible. Ultimately, this should close issue #630 .

Oct. 20, 2014: After some research, I have a slightly better idea of what I need to accomplish. These tasks might change as more information comes along -- I haven't even learned about QtTest yet.

Oct 29, 2014: After further thinking, it might not be worth it to focus on upgrading everything to Pytest just yet. For the time being, I mostly just want to get some tests done. So, I'm putting the Pytest goals on hiatus.

- [ ] Replace the Setup and Teardown functions with a pytest fixture (Hiatus)
- [ ] Adjust existing tests as necessary to conform with pytest style (Hiatus)
- [ ] Write test for click_talk
- [ ] Write test for click_add_talk
- [ ] Write test for show_save_prompt
Ok I did some more investigating and here's what I found. It's failing specifically with buttons from the commandButtons widget and half of the buttons work and the other half causes segmentation faults.

<pre>
importButton    - works
exportButton    - fails
addButton       - fails
removeButton    - works
removeAllButton - fails
searchButton    - works
</pre>

What do all the buttons that cause segfaults have in common? They all open up a new dialog box in the UI. I think this is the key issue. If you click import, remove, and search buttons those all do not cause segfaults and they also don't open a new dialog box inside the UI.

So the issue seems to have to do with the fact that a new dialog box opens. I'm guessing similar to how we have to unload FreeseerApp with the delete command, we need to do something with the new dialog windows that open otherwise it causes a segfault when we try to exit the test.

At this point I'm not sure what the right solution is but at least we know exactly what the cause is now.