QA + ui / ux - is it possible to combine these two fields within the framework of the master's?

Question

Software testing

Hello! I would be grateful if someone could help clarify my question.
At the moment I work as a tester (I only enter automation) and I study in the direction of ui / ux design in the master's program (in fact, over the year of study, I have not yet been able to formulate a suitable topic for my master's work, this is due to the fact that everything that is more traditionally for ui / ux design is already "trivial, hackneyed, no scientific novelty" - according to my teachers, who mercilessly crack down on my themes and work on them ....) .
I am already in some despair - whatever I propose as a scientific problem - was solved before me. Now a new defense of developments on a master's thesis is coming, and in fact I was left without a topic. In this regard, I had a question - is it possible to somehow connect my work with ui / ux design?
I thought a lot about what problems might be, for example, in test management systems, metrics tools, etc. But so far I have not found anything significant to identify a specific scientific problem (basically, everything comes down to a practical solution). Therefore, I am turning here in the hope of advice / hints, maybe an idea in which direction to move. Is it possible, for example, to somehow tie automation to ui / ux problems ....
I understand that perhaps my question is absurd, but I really don’t have anyone to ask for advice, all teachers only criticize, at least one would suggest where dig, but no.... Besides, I'm not yet an experienced tester to identify, perhaps, obvious problems in our work in terms of ui / ux (claiming to be a scientific solution). I will be grateful to everyone who answers.

Answer 1

So what! I took a typical topic and advanced it further by 0.001, the main thing is that its complexity should simply go to the mass

Answer 2

and give examples of topics that were rejected?
As for the intersection of QA and UI / UX, a couple of ideas:
1) at one time I wanted to have a kind of OWASP for UI / UX to link to. Some basic "hygiene" for interfaces, like having the login field autofocus on the login page, or for frequently repeated actions, try to make fewer clicks.
2) consider the impact on ui / ux on the final product, on the business. for example, I was impressed by the use case of a company that changed the arrangement of elements a little in the checkout and as a result increased profits by reducing user errors. qa in this context will be able to catch problem areas in advance? (for example, according to the checklist from the first paragraph?)
besides, "usability testing" produces many interesting links. I'm sure there have been presentations / reports on this topic somewhere, try to get inspired from there.

Answer 3

I didn’t understand, why is TMS such a unique product that it is impossible to apply generally accepted usability practices to its interface?