Details
-
Task
-
Resolution: Done
-
P2: Important
-
None
-
None
-
None
-
-
13
-
e0738a5e7 (dev), e61698bb9 (dev), d1c168f97 (dev), 9b5d12bff (dev), fd5d3e97a (dev), e1c356a11 (dev), 0ba0f6890 (dev), d57ff1f13 (dev), 365eb9964 (dev), 45809dfc2 (dev), b93c36b0d (dev), 0ae3ea9d8 (dev), 909eec11f (6.9), a51845079 (6.9), 47ce0f65f (6.9)
-
Foundation Sprint 121, Foundation Sprint 122, Foundation Sprint 123, Foundation Sprint 124
Description
tst_oauth2 and tst_deviceflow have many things in common, but sharing them is not trivial, or more aptly put, results in messy autotest code with a lot of if/elses.
However the test cases should be finegroomed if more can be shared. Possibly a new tst_authorizationcodeflow test should be introduced, and the tst_oauth2 should just focus on testing abstract oauth2 setters.
Without such refactorings, the autotests are (increasingly) hard to maintain, and contain unnecessary duplication and work effort in the long term.
Attachments
Issue Links
- resulted from
-
QTBUG-130844 [OAuth] Post "Qt 6.9 FF" items for Device Authorization Flow support
-
- Closed
-
- split from
-
QTBUG-130844 [OAuth] Post "Qt 6.9 FF" items for Device Authorization Flow support
-
- Closed
-