-
Notifications
You must be signed in to change notification settings - Fork 577
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Graphical QT Testing #1603
base: v0.6
Are you sure you want to change the base?
Graphical QT Testing #1603
Conversation
This is some bikeshead. Why don't you just write a |
79ce3c0
to
1236d24
Compare
That is the nature of automated tests, they should not open any GUI or require X, because Travis CI has no X. |
Actually @g1itch . This is the automation graphical Qt test cases. Where the script automatically opens up the Qt interface and automatically fills the inputs of the different windows and waits for the response. So, that's why I didn't use the unit tests. The main purpose of these tests is to automate the Qt interface. These tests are just like the same we use Selenium automation for the web . Thanks |
OK, I don't want to automate the Qt interface. Unsubscribed. The tests from |
@g1itch Similarly as the |
Anyway, I see no reason to introduce another argument and state variable, same for not using unittest. xvfb-run is what I searched for; need some time to find how to use it inside python. |
There are also other types of tests in addition to unit tests, so maybe it can be better with those instead. Regarding xvfb, this is what I have in the buidlbot config:
But I see you already have it in your ci branch so maybe that's enough too. |
I'm ok with writing these tests as unit tests. I also would be ok with avoiding the state variable, the problem is that the initialisation of PyBitmessage is horrible. I'm sure you'll agree it needs to be refactored to do all these things cleanly. However, this requires someone with a lot of knowledge of PyBitmessage internals and a lot of time and testing. So I would find it acceptable to have another state variable now, with the refactoring being a longer term goal. Once we have a lot of automated tests available, the refactoring should be easier to do as well. |
1016d91
to
b97aa29
Compare
a0d3b76
to
6b0ce5d
Compare
45d4f3a
to
c9e107e
Compare
c9e107e
to
288fb35
Compare
So here is my current suggestion. Write a separate initialisation routine that will replace |
Graphical Qt Testing
Initial commit for the graphical Qt tests.
Build an automated script for Qt Interface-
-Generate address with a random label
-Generate addresses with passphrases
-Send a message and checks whether the message received or not
-Add the address in the subscription list
-Add the address in the blacklist and whitelist
-Tests for setting window.
-Tests for Inbox tab QTreeWidget PopMenu
Work is in progress. Kindly give me some feedbacks