foone, 6 months ago

ugh.
this is UI automation.
here's the problem: I have like 5 years of UI automation experience, because of the DEATH GENERATOR (and let's not even talk about the older UI automation I did back in the 2000s)

and I'm trying to automate tests written by people who do not have that much experience, and they're making all the newbie mistakes

foone, 6 months ago

things like "we need to test something on menu X. So we write the test to click the Menu X button" and never considering WHAT IF MENU X IS ALREADY OPEN

foone, 6 months ago

oh this is wonderful.
if you run the entire test suite, it passes
but if you disable one of the tests, it doesn't.
Testing fewer things means it fails

foone, 6 months ago

it's because it runs the tests in order, A, B, then C.
and B puts it in a state where C will work.
but A leaves it in a state where C won't work

Cynon, 6 months ago

@foone ... and no resetting of the test state (ie, beforeeach) to keep that from happening?!?!?

foone, 6 months ago

@Cynon NOPE!

foone, 6 months ago

a software test failed because a screw wasn't tightened enough.

I hate testing sometimes

foone, 6 months ago

this test fails if you run it more than once without rebooting the whole testing system

because it's a test of the calibration system, and it fails if there is an existing calibration.

so obviously it clears the calibration at the start, right? right? RIGHT!?

foone, 6 months ago

no instead there's just a comment that says "this test will fail unless you delete this file: "

foone, 6 months ago

oh god
this IDE has two "copy name" items which are similar, like "copy X name" and "copy Y name"

"copy Y name" will modify python files if you click it.

foone, 6 months ago

speaking of python, this code manages to break python so much that foo.class and type(foo) don't work and just tell you object, but if you query foo.awlkhjertkla you get AttributeError: 'Bar' doesn't have attribute awlkhjertkla.

foone, 6 months ago

I slightly lied.
"type(foo)" doesn't actually work because THEY CLOBBERED THE BUILTIN so you actually have to do builtins.type(foo) which then doesn't work

foone, 6 months ago

oh goody
this test creates two objects in a shared persistent canvas and then checks that the object count is 2.

what happens if you run it twice, though?

coolpowers, 6 months ago

@foone I think you need to work on your naming conventions, personally

foone, 6 months ago

@coolpowers how dare you
that's my middle name

yakkoj, 6 months ago

@foone I am running hardware from Cisco right now that will fail line cards if the screws that hold them in are not at least 10 in-lb tight.

They'll do this randomly, too.

Not terribly bright for a router that's supposed to pass traffic instead of being a really expensive Red Hat box.