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)
- [ ] Refactor talkeditor.py to make it easier to test. In particular, avoid using exec_() method.
- [ ] Write test for click_talk
- [ ] Write test for click_add_talk
- [ ] Write test for show_save_prompt
I looked at your #605 comment and was wondering how you implemented it originally?

If you did what I did to quickly test and just switched out exec_() for
<pre>
d.setModal(True)
d.show()
</pre>

Then the buttons will not really do anything because show() is a non-blocking function. So you cannot evaluate an if statement immediately after show(). The program will continue to proceed since it's non-blocking thus whatever variable you are waiting on for user input will not have been processed yet.

You need to create a Qt SIGNAL/SLOT to connect the accept and cancel button clicks back to a function which will process the user input that you are waiting for after the user has provided their input.