Removed the regression test package

[grzesiek2010]

Why is this the best possible solution? Were any other approaches considered?

The regression package was a set of tests written by the QA team. It's been a while since the QA team added something there and we have decided that it will no longer be their responsibility.
I have reviewed the tests:

• removing duplicated tests
• reworking/moving test that we (developers) might still need
• removing tests that didn't make much sense from my (dev) perspective or were difficult to understand.

The test cases that were covered by the tests I've removed are still performed manually by the QA team during regression testing I belive so it shouldn't be dangerous.

How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?

It doesn't require testing.

Do we need any specific form for testing your changes? If so, please attach one.

No.

Does this change require updates to documentation? If so, please file an issue here and include the link below.

No.

Before submitting this PR, please make sure you have:

• added or modified tests for any new or changed behavior
• run ./gradlew connectedAndroidTest (or ./gradlew testLab) and confirmed all checks still pass
• added a comment above any new strings describing it for translators
• verified that any code or assets from external sources are properly credited in comments and/or in the about file.
• verified that any new UI elements use theme colors. UI Components Style guidelines

[seadowg]

@grzesiek2010 there's some conflicts here now (probably because of #6059 - sorry 😔).

[seadowg]

#5983 (comment)

[grzesiek2010]

@grzesiek2010 there's some conflicts here now (probably because of #6059 - sorry 😔).

Fixed.

[seadowg]

Github doesn't let me track where I am in a review by commit so I'll just track it in this comment. Latest commit

[seadowg]

I'm frankly finding it hard to find time to fit this in. @grzesiek2010 are you able just pull the commits after 74cbd26 onto another branch for the moment? I think this will be much easier to review and merge in chunks rather than all at once and there's no reason we need to make the change in one go.

[grzesiek2010]

I'm frankly finding it hard to find time to fit this in. @grzesiek2010 are you able just pull the commits after 74cbd26 onto another branch for the moment? I think this will be much easier to review and merge in chunks rather than all at once and there's no reason we need to make the change in one go.

Let's keep this pr. I will convert it to a draft. There is a new one that contains the commits you have reviewed #6142