Closed damithc closed 6 years ago
If somebody can report here exactly what needs to be deleted, we can downgrade this to a FirstTimer
issue.
I'm not 100% sure, but I think removing
MashupPageUiTest.java
file.
will remove the MashupPageUiTest.
Can I try this?
@AlexM9200 sure you can but there are still a few more things to remove/modify other than what @amarlearning mentioned. If you can figure them out go ahead otherwise maybe you should do a d.FirstTimers
first instead.
OK thanks i'll have a look. If I don't make a pull request within a few hours someone else can have it.
I can tell which files need to be removed, but before that, let's get some things straight first:
The mashup page is badly broken
I just checked, it is indeed broken but has a simple two-liner fix.
The test is not used for its intended purpose anyway
I never asked this before: what is the intended purpose to begin with?
If it is to manually eyeball the page (as suggested by the introduction), then this is not a "test" per se, but more like some kind of script to be run from time to time. It may be worth to be moved to scripts instead.
Yes, it is for manual eyeballing of the entire UI in one page. Previously, it used to be the last test to run and leaves the page loaded at the end of the test suite for me to inspect before I set the new version live. That no longer happens and I don't think I've inspected this page since many moons. :-p
If the maintenance cost is worth the effort, I don't mind keeping it. e.g. everytime we add a new page, we should add it to the mashup as well.
Previously, it used to be the last test to run and leaves the page loaded at the end of the test suite for me to inspect before I set the new version live. That no longer happens
This is because the said test is excluded from CI tests or staging tests (before it was removed). Possible solutions here:
If the maintenance cost is worth the effort, I don't mind keeping it. e.g. everytime we add a new page, we should add it to the mashup as well.
I will defer this decision to the new team, but judging from the number of new pages added in recent 2-3 years (less than 5?), it should not be a big issue.
I will, however, reiterate my stand that at its current state, this cannot be called a "test".
The mashup page is badly broken
How is the page supposed to look like? I've only ever known it in its current state. I'm guessing all the elements should be styled exactly as they appear in the actual pages?
@whipermr5 change the following two lines:
to:
- <link type="text/css" href="<%= FrontEndLibrary.BOOTSTRAP_CSS %>">
- <link type="text/css" href="<%= FrontEndLibrary.BOOTSTRAP_THEME_CSS %>">
+ <link type="text/css" href="<%= FrontEndLibrary.BOOTSTRAP_CSS %>" rel="stylesheet">
+ <link type="text/css" href="<%= FrontEndLibrary.BOOTSTRAP_THEME_CSS %>" rel="stylesheet">
That concludes what I said as "simple two-liner fix".
How is the page supposed to look like? I've only ever known it in its current state. I'm guessing all the elements should be styled exactly as they appear in the actual pages?
Yes.
Hey, has a decision been made on the appropriate approach or is this up to whoever submits the changes?
Let's fix it and move it into client scripts.
I'm just wondering if it has much use though? Sounds like it's more like a maintenance burden with little benefits.
@damithc @wkurniawan07 @whipermr5 @LiHaoTan Has any decision been made regarding this issue?
I'm just wondering if it has much use though
@LiHaoTan you can say the same for more than half of the current client scripts 😛
Putting on hold for now
The mashup page is badly broken and the test is not used for its intended purpose anyway. Lets get rid of it.