Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #27329 All Revisions ] Back to Issue ]
Summary 0027329: Stabilization: Overhaul the loading process (since the url is entered until the webpos has loaded)
Revision 2014-08-22 00:26 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including backbone and enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that generic initializations, backbone initializations, enyo initializations, events processing and asynchronous calls are more mixed than desirable
- Verify that the application is started to load before the javascript file has been processed
- Verify that, sometimes, there are errors and its hard to see what caused them

Insert a random fail in an asynchronous response
- Verify that there is code depending on the successful result of that asynchronous call, that is still trying to be executed

Tests
- Verify that there are login errors
- Verify that tomcat and javascript errors populate the logs

Revision 2014-08-22 00:25 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including backbone and enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that generic initializations, backbone initializations, enyo initializations, events processing and asynchronous calls are more mixed than desirable
- Verify that the application is started to load before the javascript file has been processed
- Verify that, sometimes, there are errors and its hard to see what caused them

Insert a random fail in an asynchronous response
- Verify that there is code depending on the successful result of that asynchronous call, that is still trying to be executed

Tests
- Verify that tomcat and javascript errors populate the logs

Revision 2014-08-22 00:21 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including backbone and enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that generic initializations, backbone initializations, enyo initializations, events processing and asynchronous calls are more mixed than desirable
- Verify that the application is started to load before the javascript file has been processed
- Verify that, sometimes, there are errors and its hard to see what caused them

Insert a random fail in an asynchronous response
- Verify that code depending on the successful result of that call are still trying to be executed

Revision 2014-08-17 03:22 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including backbone and enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that generic initializations, backbone initializations, enyo initializations, events processing and asynchronous calls are more mixed than desirable
- Verify that the application is started to load before the javascript file has fully loaded
- Verify that, sometimes, there are errors and its hard to see what caused them

Insert a random fail in an asynchronous response
- Verify that code depending on the successful result of that call are still trying to be executed

Revision 2014-08-17 03:20 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including backbone and enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that generic initializations, backbone initializations, enyo initializations, events processing and asynchronous calls are more mixed than desirable
- Verify that the application is started to load before the javascript file has fully loaded

Insert a random fail in an asynchronous response
- Verify that code depending on the successful result of that call are still trying to be executed

Revision 2014-08-16 15:35 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that object and enyo initializations, and asynchronous calls are interlaced
- Verify that the application is started to load before the javascript file has fully loaded

Insert a random fail in an asynchronous reponse
- Verify that code depending on the successfull result of that call are still trying to be executed

Revision 2014-08-16 15:33 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

- Verify that object and enyo initializations, and asynchronous calls are interlaced
- Verify that the application is started to load before the javascript file has fully loaded

Insert a random fail in an asynchronous reponse
Verify that code depending on the successfull result of that call are still trying to be executed

Revision 2014-08-16 12:10 by Orekaria
Steps To Reproduce Insert a console.debug in the initialization of every object (including enyo objects)
Open a new browser tab
Open the console
Insert the WebPOS url
Login
Wait until the WebPOS has loaded

Verify that object and enyo initializations, and asynchronous calls are interlaced

Insert a random fail in an asynchronous reponse
Verify that code depending on the successfull result of that call are still trying to be executed



Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker