4 ms·

This is about headless scripting for the browser, but your comment appears to be a shameless self-promotion for something unrelated.

• tudorconstantin 6y ago
  I thought it's about a knowledge base about e2e testing using playwright/puppeteer. The problem I wrote about is one that's solvable using those tools (I think and hope). It's a problem I'm trying to solve in my limited free time and I was hoping someone already have solved it, but if that's not the case and someone also finds it interesting, how should've I let people know there already is an open source playground for this, without posting the project.
  • chromedev 6y ago
    I get that but when you brought up TypeScript and React, these tools are pretty indifferent to the underlying frameworks and are primarily used to simulate web browser interactions. I suppose you could integrate them into your e2e testing automatically, but every site is different so it would likely be difficult to do anything useful.
    • tudorconstantin 6y ago
      I mentioned typescript and react (meaning jsx actually) because browsers run javascript. So the browser will have to be able to make a mapping from javascript -> jsx -> typescript in order to report correctly what was covered during the execution.
      • chromedev 6y ago
        That mapping is going to happen though regardless if it is a headless or real-user interaction. I don't think these tools are going to help with mapping unless you know what kind of interaction you want to simulate, and be able to map the entire interaction. I think tracing and logging tools would be a lot more useful and appropriate for those types of scenarios. I do think they can help with e2e testing, just not inline with the frameworks you mentioned.