[Adam Parkin, Test Podcast] Unfortunately in my specific case here that (running the server locally alongside the test) is not an option (or at least not without a lot of work to make that happen, which maybe that’s the answer :shrug).
But yes, effectively it is “test is running on one machine, code under test is running on a different machine”.
[Adam Parkin, Test Podcast] It occurs to me I’m probably misusing the term “integration test” here, in my case my tests are really “full system tests”, so maybe to tweak my question slightly: is it a good idea to generate coverage information for tests that are full system tests, and if so (or at the very least if it’s not a bad idea) how do you achieve that?
Like maybe a more concrete way of thinking of this: say you have a bunch of selenium tests that you execute against your staging environment. You want to get a sense of what parts of the overall system are exercised by those tests and which are not, how would you go about discovering that?
[David Kotschessa, Test Podcast] Say I want to do something crazy with
tox like run...well... like every version of python since 2.7. (It's an experiment and possibly blog article).
I'm confused bout the overlapping domains of:
virtual environments (I use just
tox itself (which, I guess is lke venv, but you can still use it with venv?)
Now I'm reading i might want
pyenv if I want to install all these different versions of python.
What's the simplest way?
[David Kotschessa, Test Podcast] So I guess here's where I'm confused. say I'm in an activated
venv and I install a package, say django - it installs itself in the
venv/bin/whatever folder, but not otherwise on my machine.
The python version I'm using is also in
venv/bin/python (or whatever) based on what version I'm using. Bu it's also installed globally.
So I have python 2.7 (because mac still ships with it) and 3.8 (because that's what I installed)
Soooo say I want to install python 3.2 - is there an installation method that puts it in the venv but does not install globally?
[Gabriele Bonetti, Test Podcast] Hi All, currently I run some test pipelines on jenkins completely on AWS, creating on-demand workers (jenkins slaves) when they are needed. Workers have been linux only so far but we will introduce win 10 support which needs to be tested. Have you ever tried to manage win 10 images on AWS? since there is no native image I see you have to bring your own and manage your own licenses, but looks cumbersome, how it's going to work on on-demand dynamic workers that then disappear?
So I was wondering if this is a good idea at all or there are other solutions, for example using the supported windows server 2016 / 2019 images with desktop support and that can be good enough for testing on the equivalente windows desktop.
For example I was also looking at browerstack, and there is a server -> desktop table, except for windows 10 :-) https://www.browserstack.com/question/478#:~:text=Home%20Support%20Live-,Is%20web%20testing%20on%20Windows%20Server%20edition%20the%20same%20as,remote%20access%20to%20our%20customers.&text=For%20Windows%2010%2C%20we%20use,which%20is%20a%20Desktop%20edition.