Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

testLocalPrintingToggle() Failure #23

Closed
marctan opened this issue May 4, 2016 · 5 comments
Closed

testLocalPrintingToggle() Failure #23

marctan opened this issue May 4, 2016 · 5 comments
Assignees

Comments

@marctan
Copy link
Contributor

marctan commented May 4, 2016

The failure is at line 2108 of testcert.py
The function was trying to find the change button from the chrome print dialog but this dialog is not visible/open, thus the test failed.

I believe the print dialog box must be visible first before calling 'SelectPrinterFromPrintDialog()'.

@kdlucas and I already have an email thread about this issue.

Thanks
-Marc

@kdlucas
Copy link
Contributor

kdlucas commented May 26, 2016

Marc,

We made some changes to testcert.py, is this still an issue?

@marctan
Copy link
Contributor Author

marctan commented Jun 2, 2016

Kelly,

Unfortunately, this is still not fixed.

I'm inserting our previous original email thread regarding this issue below for more information:

Marc: My second concern is the testLocalPrintingToggle(). This test failed. The failure was on testcert.py:2108. It failed since it was trying to find the change button or (destination-settings-change-button) that does not exists. I believe the fix for this is, we should call chrome.Print() first before calling this line:
testcert.py:2108: found = chrome.SelectPrinterFromPrintDialog(self.printer, localprint=True)

Kelly: For the 2nd issue, it shouldn't be calling chrome.Print() first, as the change button is not related to printing. When you're looking at the screen, do you see the Change button?

Marc: The change button can be seen in the chrome "print dialog". Since we already closed the print dialog at line 2100 of testcert.py, the function chrome.SelectPrinterFromPrintDialog(self.printer, localprint=True) in line 2108 of testcert.py failed because it is expecting the "print dialog" to be there.

Kelly: Marc, Ok, I understand better now. Please file an issue on GitHub and I'll address it there:

Hope this helps.

Thanks,
Marc

@marctan
Copy link
Contributor Author

marctan commented Jun 21, 2016

Hello Kelly,

Do you have an update on this?

Thanks!

@kdlucas
Copy link
Contributor

kdlucas commented Jun 22, 2016

I think the fix here is simply to put chrome.print() in line 2107. I've made the change, so please verify if this works.

@kdlucas kdlucas self-assigned this Jun 22, 2016
@marctan
Copy link
Contributor Author

marctan commented Jun 23, 2016

This is now fixed.

Thanks

@marctan marctan closed this as completed Jun 23, 2016
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants