Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Can you talk about your team's motivations for improving headless mode? Any particular use cases in mind?


Here are two of them: -Test reproducibility -Automated configuration rollouts in enterprise environments


Improving test environments is a huge upside. I haven't worked on browser automation in nearly a decade, but finding ways to work around shortcomings in the headless environment used to burn a lot of time on that team. I know of many small teams which made deliberate decisions NOT to do any browser automation tests (e.g. Selenium) because some issues required testing hooks in production code.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: