{"id":462,"date":"2007-02-14T08:56:03","date_gmt":"2007-02-14T13:56:03","guid":{"rendered":"http:\/\/josh.ev9.org\/weblog\/archives\/462"},"modified":"2007-02-14T10:12:06","modified_gmt":"2007-02-14T15:12:06","slug":"screen-placement-testing-tool","status":"publish","type":"post","link":"http:\/\/josh.ev9.org\/weblog\/archives\/462","title":{"rendered":"Screen-placement testing tool"},"content":{"rendered":"

All sorts of automated tests happen on projects at ThoughtWorks<\/a>. There are Unit Tests, Functional tests, GUI tests, and others that make sure the software we’re building runs well from the most back-end function all the way to the user’s interface.<\/p>\n

One thing we don’t test, however, is where particular elements land on a screen. We make sure that the drop-down box you were expecting to be on a given page is there, and that it holds the values that should be there, but we don’t make sure it lines up right next to the label that explains what it is for.<\/p>\n

I’ve brought this up a few times while on projects, and developers have told me that we don’t test for screen position because we just can’t<\/em>. I wonder how true this is.<\/p>\n

When it comes to visual design, the placement of elements on an interface does matter. When doing a visual assessment, it’s important to me that all the pixels on the left-hand side of the screen are aligned to a grid line. It’s important that that drop-down is placed right next to its label. It’s vital that the company’s logo is always on the top left. And even on a low resolution monitor, this input box needs to align with the others. On and on…there are plenty examples.<\/p>\n

I understand that testing for screen position is a hard problem, and is impossible with our current automated testing tools. But is it really impossible altogether?<\/p>\n

Hey all you developers out there, weigh in with your opinions. And for anybody else out there…how important would a tool that does this be to you?<\/p>\n","protected":false},"excerpt":{"rendered":"

All sorts of automated tests happen on projects at ThoughtWorks. There are Unit Tests, Functional tests, GUI tests, and others that make sure the software we’re building runs well from the most back-end function all the way to the user’s interface. One thing we don’t test, however, is where particular elements land on a screen. […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"nf_dc_page":"","_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[16,17,23,21,12,13],"tags":[],"class_list":["post-462","post","type-post","status-publish","format-standard","hentry","category-agile-development","category-design","category-free-design-idea","category-professional","category-technology","category-thoughtworks"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t