Cache Owner Dashboard heading change

[+barefootjeff]

What's happened to the heading in the Cache Owner Dashboard?

 

Before:

 

 

Now:

 

 

As well as the poor contrast between the grey labels and the dark green background, these new button things (if that's what they're meant to be) are also forcing the columns to be of uniform width instead of before when the columns with narrower information fields, like Finds, Favourites and DNFs, were narrower.
 

How is this an improvement?

[+niraD]

1 hour ago, barefootjeff said:

How is this an improvement?

It forces horizontal scrolling (because the columns with narrow data take up far more space than they need). Isn't that an improvement?

[Blue Square Thing]

Oh dear.

 

That's really not great. No need for the green and some of the cols are far too wide. I shouldn't need to horizontally scroll on an even vaguely wide window *ever*, let alone for something like this.

[+MartyBartfast]

Agree, very poor,

 

Also the map icon is labelled "map your qeocaches" but when you click it it takes you to the search page.

 

Whoever looked at that and thought that's good enough to go live?

[+MartyBartfast]

qg

9 hours ago, MartyBartfast said:

Also the map icon is labelled "map your qeocaches"

Looking again I think that is a "g" but part of the descender is truncated so it looks more like a q

Edited Saturday at 06:47 PM by MartyBartfast

[Bl4ckH4wkGER]

18 hours ago, barefootjeff said:

How is this an improvement?

 

It's not, it's a bug in the CSS styles for that page.

 

Thanks for bringing it to our attention. It's been passed on to the appropriate parties.

[+MartyBartfast]

53 minutes ago, Bl4ckH4wkGER said:

It's not, it's a bug in the CSS styles for that page.

Going back to my point above, surely the process for releasing code to live requires that someone checks the changes in test before they go into the live site, and then having gone live someone checks the live site?

 

If that's the case how can it be that this wasn't picked up until one of your customers spotted it?

 

 

[Bl4ckH4wkGER]

6 hours ago, MartyBartfast said:

Going back to my point above, surely the process for releasing code to live requires that someone checks the changes in test before they go into the live site, and then having gone live someone checks the live site?

 

If that's the case how can it be that this wasn't picked up until one of your customers spotted it?

 

I actually wrote up a bug report for this on the 13th, believe it or not, while testing something else. So we've been aware, it's just not a drop everything to fix it type of bug.

 

For any code change, there's a mix of manual and automated testing involved.

 

Unit tests are written by developers to help guide their development and make sure that they build what is asked.

 

Further manual tests by an QA engineer are used to validate the acceptance criteria of any particular ticket. As an example: is there a button now where there was no button before in space X.

 

Automated tests are used to validate certain essential features of the website. As an example: can a player create an account, can they sign in, can they run a search that returns results, etc.

 

All of this happens at multiple stages:

- in a test environment

- during deployment

- in production once things are live

 

Catching that a style change in area A had an unintended impact on a otherwise unrelated area B would require some degree of "turning over every stone" of the website every time you make any kind of change. That's not feasible for any company.

 

Testing styles outside of the changed area or essential areas is generally uncommen. The focus of testing is generally to make sure that "a button is there and works". Visual mismatches 9 times out of 10 tend to be annoyances that are then prioritized as such.

 

Edited Sunday at 01:01 AM by Bl4ckH4wkGER

[+GeoTrekker26]

Thanks for the peek through the developer’s door!