Confirmed users
508
edits
Privacy/Reviews/CaseConductor: Difference between revisions
Jump to navigation
Jump to search
→Architecture
| Line 44: | Line 44: | ||
** These users can do everything from above, and can also manipulate user accounts. | ** These users can do everything from above, and can also manipulate user accounts. | ||
Results: | '''Results:''' | ||
All users can login and see results of executed test cases. They can see what passed, what didn't and what cases were not clear. | All users can login and see results of executed test cases. They can see what passed, what didn't and what cases were not clear. Users can also see % coverage for test runs. Users can also "drill down" and see if all the environments for a specific test case of a run have been executed. | ||
'''History''': Originally this product was designed to be in two parts. A "Platform" written in Java providing REST endpoint APIs and a "User Interface" written in Django. Despite some people's investment in this relationship with uTest and the separation of the two parts, eventually it was determined that this architecture was untenable. At this point (Nov 2011) we decided to re-architect as pure Django. | '''History''': Originally this product was designed to be in two parts. A "Platform" written in Java providing REST endpoint APIs and a "User Interface" written in Django. Despite some people's investment in this relationship with uTest and the separation of the two parts, eventually it was determined that this architecture was untenable. At this point (Nov 2011) we decided to re-architect as pure Django. | ||