I should learn that the effort for maintainability of automation testing that has been created is quite time consuming and energy consuming, with the current weekly sprint situation, it’s quite challenging to maintain it. On the other hand, if we don’t take the time to do the maintenance, the process of doing automation testing will be hampered by flaky tests and resulting in a brittle results, and we tend to focus on fixing the flaky test.
i don’t think this is a bad news since i got some lesson learned here, also i’ve read about testing in Google team, where their team also got at least 1 in 7 test cases experiencing flaky test — and this can also happen everywhere not just in the software testing fields.
good to read how google handle and mitigate the flaky tests ::
https://testing.googleblog.com/2016/05/flaky-tests-at-google-and-how-we.html