pavelfeldman
commented
1 year ago Why was this issue closed?
Thank you for your involvement. This issue was closed due to limited engagement (upvotes/activity), lack of recent activity, and insufficient actionability. To maintain a manageable database, we prioritize issues based on these factors.
If you disagree with this closure, please open a new issue and reference this one. More support or clarity on its necessity may prompt a review. Your understanding and cooperation are appreciated.
Let us know what functionality you'd like to see in Playwright and what your use case is: This issue relates to #15258 which was recently closed, but unfortunately not solved. My DevOps team and I are working in Azure DevOps cloud. for a fortune 100 company. We have been researching solutions to export the results of Playwright Reporter out to Microsoft Teams (or Enterprise Outlook) without any success since the solutions offered in Issue#15258 are not permitted by the business. We have to make it work with Azure DevOps cloud. We ultimately want to evince to the executive leadership that controls the finances - like Gandalf on the bridge saying "You shall not pass" (I.e. Our DevOps team getting money for more projects lol) - so this simple implementation of time/date stamp would help use prove our use case as to why our company needs to implement more automation for better value to the end-user. The origin of this idea was derived at a Sprint Planning meeting for a time stamp to be on the Playwright report (of when the test execution occured).
And the reason for that request is this: 1) We are running smoke/regression tests overnight when there is no one on the network. However, as it is in very large organizations, there are often times when outages of service, or resetting servers for maintenance occurs. Therefore, it would be really helpful to know exactly what time the test execution happened overnight, so if, per se, that a lot of tests failed, was it because of outage(?), or the result of a new feature addition that caused a significant majority of the previously working tests to break? Any time saved from having to log dive, or spent troubleshooting, I think we all can agree is a great feature. 2) Having the time and date stamp also can permit the dev/tester to export that result to management to verify automation is up and working. 3) Since the feature of mocking geolocation already exists within Playwright, having the actual time stamp of your local test execution on the Playwright Report is also handy to have.
Do you think others might benefit from this as well? Being that smoke and regression tests are very common in our industry, the answer to the aforementioned question is a resounding YES! It can help everyone by implementing a time and date stamp on the Playwright report. And being a former dev, I know there are already existing methods built into some programming languages: GetLocalDate method in Java, for example. So the development of this may be like a one point story for your dev team.
Sidebar: I'm really really looking forward to the day when the joint venture of Playwright witlh Microsoft Teams/Outlook so that Playwright's report can export out the results of a test execution via Teams, or Outlook, so members of an application development working in DevOps can see the results in the morning to know what is broken and what is not broken, way ahead of stakeholders finding out and creating incident reports for us. Plus, how cool this feature is with being able to mitigate potential incident repots to solve (since we would get advance notice from the overnight test execution), Anything that reduces incident tickets, makes our lives easier, and creates more value to the business is an excellent update/feature addition! :)