Timeline for What are the best practices for automating test cases in a dynamic web application with frequently changing UI elements?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 24 at 8:07 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Dec 25, 2023 at 7:32 | answer | added | Bosco Corriea | timeline score: -1 | |
| Sep 27, 2023 at 21:09 | comment | added | Lee Jensen | Also, ideally, you don't want to test content since it changes all the time. You want to focus more on the usability of the software regardless of content. | |
| Sep 25, 2023 at 21:21 | comment | added | Lee Jensen | Welcome to the community. I think it would help if you better clarify what you mean by "dynamic." Most, if not all, web apps these days are dynamic, meaning they use Async processes, event/message queues, user-supplied data (social media, comments), content changes (blogs), etc. How are you using "dynamic" differently or is it the same as "frequent UI elements changes?" | |
| Sep 20, 2023 at 12:17 | comment | added | Kate Paulk | Welcome to SQA Stack Exchange. You'll probably get better results if you split each of your points into a separate question. This will allow you to get answers specific to each point. | |
| S Sep 20, 2023 at 12:14 | history | suggested | jonrsharpe | CC BY-SA 4.0 |
Improve formatting, trim fluff
|
| Sep 20, 2023 at 9:55 | review | Suggested edits | |||
| S Sep 20, 2023 at 12:14 | |||||
| S Sep 20, 2023 at 9:25 | review | First questions | |||
| Sep 20, 2023 at 10:12 | |||||
| S Sep 20, 2023 at 9:25 | history | asked | gregbowers | CC BY-SA 4.0 |