3 ms·

> Ths context is that testing is a solved problem. The only problem that is solved is running multiple browsers in VMs in a cloud. Everything else is anyone's

> Ths context is that testing is a solved problem. The only problem that is solved is running multiple browsers in VMs in a cloud. Everything else is anyone's guess. To come up with an automated test for the problem in the OP you have to be a) aware of the problem and b) have a way to test that scrollbars do/don't appear. Good luck with that.

IncRnd 6y ago
> The only problem that is solved is running multiple browsers in VMs in a cloud. Everything else is anyone's guess. That false hyperbole. Just because you do not know something, that doesn't mean that nobody else does. > To come up with an automated test for the problem in the OP you have to be a) aware of the problem and b) have a way to test that scrollbars do/don't appear. Good luck with that. No luck is needed, just tests. You may not realize, but test frameworks already exist for testing the screen for the presence of UI elements. That is how dialog boxes are clicked in tests. This is literally solved.
- dmitriid 6y ago
  > Just because you do not know something, that doesn't mean that nobody else does. For the third time you've failed to show how to test for the problem described in OP. It tells me that you don't know > test frameworks already exist for testing the screen for the presence of UI elements Which ones test for the presence/absence of scrollbars?
  - IncRnd 6y ago
    Honestly, it seems like you are playing a game. Did you perform a search of tools that can test ui? There are lots of them. I find it hard to believe that you think there aren't any. That's like saying that compilers don't compile C code anymore, because you only compile C++. I see our testers doing this all the time - but I don't know what libraries they use. I know the testers at our shop do it with an house built framework as well as with commercial ones. On our company's security team, various people have scripted UI exploits using selenium or appium. I just asked one of the people familiar with those two tools I mentioned, and she said it would take her a few minutes. These are commodity tools. There is nothing special with any of them.
    - dmitriid 6y ago
      > Honestly, it seems like you are playing a game. Did you perform a search of tools that can test ui? There are lots of them. It would'be been so easy to just answer the question I asked. Instead, it's now a thread of non-answers and thinly veiled ad-hominem attacks. The rest of your long answer is once again working hard on avoiding the answer. > I find it hard to believe that you think there aren't any. I didn't say there weren't any. I asked, "which ones let you test the problem in OP". > I see our testers doing this all the time - but I don't know what libraries they use Ah, my assumption that you don't know what you're talking about is proven correct. > On our company's security team, various people have scripted UI exploits using selenium or appium Question: scrollbars. "Answers": tools click on buttons, scripting security exploits, I don't know what libraries testers are using. Ignorance is bliss, isn't it? > and she said it would take her a few minutes. Given your answers in this thread, I seriously doubt your ability to ask a proper question to "the people familiar with the tools". Especially given the fact that you don't know what libraries testers use and that you, apparently, don't do any testing yourself. See, frontend testing is very far from being "a solved problem". Especially for quirks as described in OP. But you wouldn't know because you, well, don't know. > These are commodity tools. There is nothing special with any of them. Indeed they are. Indeed there is nothing special. And this still doesn't answer the question.
      - IncRnd 6y ago
        Except that I did answer as to specific toolkits - with two answers for two separate kits. You used a lot of words to make it seem otherwise. As you yourself wrote, "Ignorance is bliss, isn't it?"
        dmitriid 6y ago
        > Except that I did answer as to specific toolkits - with two answers for two separate kits You din't, really. On the third attempt you said "I see our testers doing this all the time - but I don't know what libraries they use" and "various people have scripted UI exploits using selenium or appium. I just asked one of the people familiar with those two tools" This shows that you started this entire argument with very bad faith. You berated me for not knowing something while you yourself: - don't do frontend testing using frontend testing tools - you don't know what tools your testers use - you assume some capability of some tools only because "you talked to people familiar with them" which further shows that you yourself are not familiar with them. On the other hand, unlike you, I know what I'm talking about. Granted, I haven't used these tools extensively, but I did use them, and I'm well aware of their limitations. All you have is, well, empty words.

IncRnd 6y ago

> The only problem that is solved is running multiple browsers in VMs in a cloud. Everything else is anyone's guess. That false hyperbole. Just because you do not know something, that doesn't mean that nobody else does. > To come up with an automated test for the problem in the OP you have to be a) aware of the problem and b) have a way to test that scrollbars do/don't appear. Good luck with that. No luck is needed, just tests. You may not realize, but test frameworks already exist for testing the screen for the presence of UI elements. That is how dialog boxes are clicked in tests. This is literally solved.

dmitriid 6y ago
> Just because you do not know something, that doesn't mean that nobody else does. For the third time you've failed to show how to test for the problem described in OP. It tells me that you don't know > test frameworks already exist for testing the screen for the presence of UI elements Which ones test for the presence/absence of scrollbars?
- IncRnd 6y ago
  Honestly, it seems like you are playing a game. Did you perform a search of tools that can test ui? There are lots of them. I find it hard to believe that you think there aren't any. That's like saying that compilers don't compile C code anymore, because you only compile C++. I see our testers doing this all the time - but I don't know what libraries they use. I know the testers at our shop do it with an house built framework as well as with commercial ones. On our company's security team, various people have scripted UI exploits using selenium or appium. I just asked one of the people familiar with those two tools I mentioned, and she said it would take her a few minutes. These are commodity tools. There is nothing special with any of them.
  - dmitriid 6y ago
    > Honestly, it seems like you are playing a game. Did you perform a search of tools that can test ui? There are lots of them. It would'be been so easy to just answer the question I asked. Instead, it's now a thread of non-answers and thinly veiled ad-hominem attacks. The rest of your long answer is once again working hard on avoiding the answer. > I find it hard to believe that you think there aren't any. I didn't say there weren't any. I asked, "which ones let you test the problem in OP". > I see our testers doing this all the time - but I don't know what libraries they use Ah, my assumption that you don't know what you're talking about is proven correct. > On our company's security team, various people have scripted UI exploits using selenium or appium Question: scrollbars. "Answers": tools click on buttons, scripting security exploits, I don't know what libraries testers are using. Ignorance is bliss, isn't it? > and she said it would take her a few minutes. Given your answers in this thread, I seriously doubt your ability to ask a proper question to "the people familiar with the tools". Especially given the fact that you don't know what libraries testers use and that you, apparently, don't do any testing yourself. See, frontend testing is very far from being "a solved problem". Especially for quirks as described in OP. But you wouldn't know because you, well, don't know. > These are commodity tools. There is nothing special with any of them. Indeed they are. Indeed there is nothing special. And this still doesn't answer the question.
    - IncRnd 6y ago
      Except that I did answer as to specific toolkits - with two answers for two separate kits. You used a lot of words to make it seem otherwise. As you yourself wrote, "Ignorance is bliss, isn't it?"
      - dmitriid 6y ago
        > Except that I did answer as to specific toolkits - with two answers for two separate kits You din't, really. On the third attempt you said "I see our testers doing this all the time - but I don't know what libraries they use" and "various people have scripted UI exploits using selenium or appium. I just asked one of the people familiar with those two tools" This shows that you started this entire argument with very bad faith. You berated me for not knowing something while you yourself: - don't do frontend testing using frontend testing tools - you don't know what tools your testers use - you assume some capability of some tools only because "you talked to people familiar with them" which further shows that you yourself are not familiar with them. On the other hand, unlike you, I know what I'm talking about. Granted, I haven't used these tools extensively, but I did use them, and I'm well aware of their limitations. All you have is, well, empty words.