pytest test_download_files.py --headless works for me on https://github.com/seleniumbase/SeleniumBase/blob/master/examples/test_download_files.py
10 replies
self.driver.quit().
<div _ngcontent-bya-c1="" aria-labelledby="mySmallModalLabel" class="modal fade bs-example-modal-sm in" id="messageboxModal" role="dialog" tabindex="-1" style="display: block;">
<div _ngcontent-bya-c1="" class="modal-dialog modal-sm" role="document">
<div _ngcontent-bya-c1="" class="modal-content">
<div _ngcontent-bya-c1="" class="modal-header">
<button _ngcontent-bya-c1="" aria-label="Close" class="close" type="button"><span _ngcontent-bya-c1="" aria-hidden="true">×</span></button>
<h4 _ngcontent-bya-c1="" class="modal-title" id="myModalLabel">mySonitrol</h4></div>
<div _ngcontent-bya-c1="" class="modal-body"> A single facility must be selected to perform this action. </div>
<div _ngcontent-bya-c1="" class="modal-footer">
<button _ngcontent-bya-c1="" type="button">OK</button>
<!---->
</div>
</div>
</div>
</div>
</son-messagebox>
In summary, if you're about to hit a page with a pop-up, you should use
self.find_element(SELECTOR).click() instead of self.click(SELECTOR) for the action that takes you to the pop-up. This is because self.execute_script(JAVASCRIPT) automatically closes any pop-ups, (which is used in self.wait_for_ready_state_complete(), which is called after most SeleniumBase actions to make sure the page is done loading before interacting with elements, thus improving test reliability.
--reuse-session which will make all the tests run through the same browser window without closing the window and opening a new one. Add --crumbs when using that to clear any cookies between tests; otherwise, if you're already logged into a website in one test, you'll still be logged in when the next test runs.
Hmm... does SeleniumBase edit anything called suid? When trying to run the tests inside Selenoid, the session ends midway through the test with the following output from Chrome.
2020-10-26T23:04:57.984420392Z [1603753497.984][INFO]: [266bb50ca1589e1a96e17c3cf53806f4] COMMAND Quit {
2020-10-26T23:04:57.984506525Z
2020-10-26T23:04:57.984515270Z }
2020-10-26T23:04:58.040384893Z [1026/230458.039896:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
2020-10-26T23:04:58.040441360Z Most likely you need to configure your SUID sandbox correctly
2020-10-26T23:04:58.055761281Z [1026/230458.046939:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
2020-10-26T23:04:58.055830692Z Most likely you need to configure your SUID sandbox correctly
It seems like setting chrome arguments to disable suid sandbox stopped the random driver exit.
Looks like the fix you used in https://stackoverflow.com/a/60549015 did the trick.
Hi @ClancyDamon_twitter , I'm trying to fully understand your situation. You can have custom setup steps around your subclasses where you can specifically set initializations. For example, you can run custom setup code after calling Python super in this example: https://github.com/seleniumbase/SeleniumBase/blob/master/examples/boilerplates/base_test_case.py
The same will work for multiple subclasses. It's just Python at that point. If that's not enough, you can also pass data on the command-line when running your tests. Example:
--data=DATA # (Extra test data. Access with "self.data" in tests.)
--var1=DATA # (Extra test data. Access with "self.var1" in tests.)
--var2=DATA # (Extra test data. Access with "self.var2" in tests.)
--var3=DATA # (Extra test data. Access with "self.var3" in tests.)And since you're already using DDT, you probably have already seen the example with File I/O for getting data for tests: https://github.com/seleniumbase/SeleniumBase/blob/master/examples/boilerplates/file_parsing/parse_files.py