To make sure your calendar, event reminders, and other features are always
correct, please tell us your time zone (and other details) using the
drop-down menus below:
Set Date/Time format:
In 12 Hour format the hours will be displayed as 1 through 12 with “a.m.” and “p.m.”
displayed after the time (ex. 1:00p.m.). In 24 hour format the hours will be displayed as 00 through 23 (ex. 13:00).
You can always change your time zone by going to your Account Settings.
Use the dropdown menu to view the events in another time zone. The primary time zone will be displayed in parentheses.
Use the dropdown menu to view the events in another time zone. The primary time zone will be displayed in parentheses.
Visiting Melto Mily(username: meltonemily753)
Create a new Discussion Topic
Tag
Please wait...
Select a Color
Manage Applications
Check the items that you want displayed. Uncheck all to hide the section.
Calendars
Files
Addresses
To Dos
Discussions
Photos
Bookmarks
The “Switch Navigator” button will no longer be available after February 14, 2017.
Please learn more about how to use the new Navigator by clicking this link.
Creation date: Sep 29, 2026 7:11am Last modified date: Sep 29, 2026 7:11am Last visit date: Oct 9, 2026 3:38pm
1 / 20 posts Displaying comment thread
Sep 29, 2026 ( 1 post )
9/29/2026
7:11am
Melto Mily (meltonemily753)
At some point, every growing product seems to hit the same problem: the automation suite gets bigger, but confidence does not improve at the same speed.
More tests can mean longer pipelines, more maintenance, more flaky failures, and more time spent figuring out whether a failed build is a real regression or just another unstable test.
For me, the interesting part is not how to automate more, but how to scale test automation without making releases slower.
A few practices seem especially useful:
keep critical tests fast and separate from the full regression suite;
avoid duplicating the same logic across dozens of scenarios;
use API-level checks where full UI automation is unnecessary;
parallelize execution where possible;
review flaky tests as an engineering problem, not as background noise;
keep test data and environments predictable.
It also seems important to review the suite regularly. Old tests can remain for years even after the product logic changes, and eventually the suite starts carrying a lot of unnecessary weight.
Zoolatech has written about how to scale test automation in products with many variants, which is an interesting case because the number of possible test combinations can grow very quickly.
For teams working with large automation suites, what helped you most: better framework design, smarter test selection, parallel execution, or simply removing low-value tests?
Attach this discussion to an event, task, or address
You can attach a link to this discussion to an event in your Calendar, a task in your To Do list or an Address. Check the boxes below for the data you want to
bring into the event’s or task’s description, and then click “Select text to copy” to have the next event or task you create or edit have the discussion text and link.
