Appium with Selenium (or XCUITest for iOS) will shorten your life expectancy and grow you some grey hairs, but there is no other better alternative for testing at user level. It is highly unreliable and each new phone OS version will tend to break your automation
As for finding devices there are a few cloud providers like xamarin or perfecto (never really worked with them in production) that gives you remote access to a lot of real devices and software versions
Having said that try to divert more testing towards lower levels- unit tests, testing on simulators, integration tests with a full phone and browser etc.
> I would also suggest to consider the Netherlands
Unless you want to become a citizen, you'll need to learn Dutch (which is a good thing IMHO but some disagree) and renounce your other citizenship.
Sweden has an even simpler system, if the employer can prove that you are needed (and for most professions reading here that's less than trivial) you are almost guaranteed to get permanent residency in 4 years and become a citizen in 5 years if you want to
You can get permanent residence after 5 years in the Netherlands too, and the language level required is pretty basic. It's not very hard to pass the required language tests within 5+ years.
The limit to one nationality is maddening, however.
I just moved to the Netherlands after four years of university in the US and a few years of unsuccessful H1B applications. It's fantastic and a lot less stressful than the US!
Because it is deeply arbitrary. Plenty of people can have dual nationalities in the Netherlands, just not me. Even the Dutch Queen has two nationalities. If I married a Dutch person I could become Dutch and have two nationalities, no problem. Hopefully the law will be changed...there has been talk of it.
I'm already eligible to apply for Dutch citizenship...I'm a well-integrated contributing member of society who would love to spend the rest of my life in the Netherlands. I tick all the boxes. I want to be able to vote and have representation (I'm a taxpayer as anyone else, after all). I want to spend the rest of my life here. But it's not limited to the Netherlands...I dearly want to become European. Dutch citizenship would give me the right to live and work anywhere in the EU (and plenty of other EU countries have no issues with people having two nationalities).
I can't give up my US citizenship because of family and other ties. If I needed to return to the US for an extended time (e.g. more than a couple months) to, for example, take care of my aging parents, I would lose everything I've worked towards in the Netherlands. The residence clock would reset and I'd have to find a new highly-skilled job and start all over. Same if I ever wanted to take a (temporary) job in another country. And if you renounce US citizenship, it's hard to ever visit the US again.
how is it defined ? suppose someone is driving 100 km/h on the left lane while the right lane is free and you approach from behind doing 150- should you stay at the left and wait for slow car to move right ?
Believe me, after a few seconds of waiting I always pass slowly on the right. It might not be legally perfect, but is the accepted way of handling drivers that are an obstacle on the left.
Both taking over on the right and not moving to the left (when you can) are traffic offenses and will be fined when observed by (often unmarked) police cars. In the Netherlands, where there are similar rules, driving closely behind another car, not observing the two seconds distance rule, is also a traffic offense.
Flaky tests are indeed a big issue, the main concern being loss of confidence in the results.
The otherwise good advice for randomization has its drawbacks-
- it complicates issue reproduction, especially if the test flow itself is randomized and not just the data
- the same way it catches more issues, it might as well skip some
Something else that was mentioned but not stressed enough is the importance of clean environment as the basis for the test infrastructure.
A cleanup function is nice but using a virtual environment, Docker or a clean VM will save you a lot of debugging time finding environmental issues. The same goes for mocked or simplified elements if they contribute to the reproducibility of the system- a simpler in-memory database can help re creating a clean database for each test instead of reverting for example
Sometimes it's the code that is flaky and not the test.
In case of concurrent execution there are a only a few reasonably working tricks like Relacy and other exhaustive ordering checkers as well as formal proofs.
Neither is cheap to use, so you will always get flaky tests there - or rather tests that do not always fall.
if the code is flaky then I have earned my pay honestly, this is a problem that should be solved.
Subtle concurrency issues are indeed very difficult to be found debugged and reproduced and randomization could help with that simply by covering more space.
I agree I think a large majority of flaky tests, for me at least, stems from some variability in the initial conditions of the test. It is good to uncover all the dependencies!
If it's the test that is flaky. But it means that if production is not extremely consistent, you will see these effects live. Better handle them correctly.
Probably drivers from the local transit union. I've seen/read about (union) activists doing some crazy things and it wouldn't surprise me that someone or some people would try to show with their life that this is a bad idea and therefore shouldn't replace a human driven system.
Do you have any data to back the assertion that this was about unions?
My gut says that it’s more probable that it was the hacker news crowd trying to test the technology, but I have to admit to have absolutely no data to support this assertion, either.
Was it on the streets, with no traffic blocking ? I took the same kind of shuttles as part of an experiment, but it was on a very specific path that was shared with pedestrians, not on the road.
They ran a test in Gothenburg as well at one of the university campuses. And while some of the roads they ran on where technically public car roads, they where small back roads across campus that see very little car traffic.
> That's not to say that SHiELD, at least as described presently, doesn't have limitations. A turreted laser can only ever engage one target at a time and there is the aforementioned risk of atmospheric disruptions reducing the beam's range and efficacy
So to intercept 20 missiles you'll need 20 expensive "turrets", your enemy knows how many "turrets" you have and can easily flood it with more cheap missiles.
Also remember that target destruction is not instantaneous, this limits the amount of targets per "turret" and the minimum range.
> So to intercept 20 missiles you'll need 20 expensive "turrets", your enemy knows how many "turrets" you have and can easily flood it with more cheap missiles.
That was Soviet Frontal Aviation's strategy for dealing with carrier battle groups as far back as the 60s. It's certainly in the DOD's considerations, and it isn't as easy as it sounds. For starters, you need to let the firing platform get within range to being with.
