[
https://issues.apache.org/jira/browse/AURORA-24?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13990271#comment-13990271
]
Suman Karumuri commented on AURORA-24:
--------------------------------------
The idea behind this task is to make the UI self-sufficient so that we can run
it with out a scheduler running in the backend. This will make in turn produce
a few benefits:
a) We can just run the scheduler with the dummy data for local testing.
b) Run the UI that makes thrift calls to a test/staging or production server
(useful for debugging UI issues with production data, test the UI with
production data)
c) We can just run the UI independent of the scheduler as a separate component
if needed.
d) Such a stand alone setup is also important if we want to run selenium tests
and jasmine unit tests.
> Build a standalone UI
> ---------------------
>
> Key: AURORA-24
> URL: https://issues.apache.org/jira/browse/AURORA-24
> Project: Aurora
> Issue Type: Task
> Components: UI
> Reporter: Suman Karumuri
> Priority: Trivial
>
> Build a stand alone UI client that works with dummy data. Such a UI is useful
> for developing the UI without running a scheduler backend. It will also
> improve the development speed considerably an also allow us to build the UI
> and the backend in parallel. In future the mock data can also be used for end
> to end testing of the UI.
> Once such a UI is built, we can also get rid of the IsolatedScheduler code, a
> special case built to mock test the old UI.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
