Openbravo Issue Tracking System - Openbravo ERP | ||||||||||||
View Issue Details | ||||||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | |||||||
0017037 | Openbravo ERP | A. Platform | public | 2011-05-06 10:35 | 2011-06-03 13:03 | |||||||
Reporter | elopio | |||||||||||
Assigned To | mtaal | |||||||||||
Priority | high | Severity | major | Reproducibility | always | |||||||
Status | closed | Resolution | fixed | |||||||||
Platform | OS | 5 | OS Version | |||||||||
Product Version | pi | |||||||||||
Target Version | Fixed in Version | |||||||||||
Merge Request Status | ||||||||||||
Review Assigned To | ||||||||||||
OBNetwork customer | No | |||||||||||
Web browser | ||||||||||||
Modules | Core | |||||||||||
Support ticket | ||||||||||||
Regression level | ||||||||||||
Regression date | ||||||||||||
Regression introduced in release | ||||||||||||
Regression introduced by commit | ||||||||||||
Triggers an Emergency Pack | No | |||||||||||
Summary | 0017037: Improve testability of collapsible sections | |||||||||||
Description | For the automation framework, it is not so clear how to tell what is the corresponding section for a given field. It is possible to loop on the fields array of the OBForm object, looking for all the OBSectionItem objects. And then get the itemIds array of those objects and check if my field is there. But this is slow and not so nice. | |||||||||||
Steps To Reproduce | ||||||||||||
Proposed Solution | It would be much easier if the fields could contain a reference to the OBSectionItem they belong to. For example, on the Sales Invoice Header tab, do something like: window.OB.TestRegistry.registry["org.openbravo.client.application.ViewForm_263"].getField('documentStatus').section and get the OBSectionItem corresponding to the Status section. There might be other possible and easier solutions. This is just the suggestion that came to my mind. | |||||||||||
Additional Information | ||||||||||||
Tags | testability | |||||||||||
Relationships |
| |||||||||||
Attached Files | ||||||||||||
Issue History | ||||||||||||
Date Modified | Username | Field | Change | |||||||||
2011-05-06 10:35 | elopio | New Issue | ||||||||||
2011-05-06 10:35 | elopio | Assigned To | => mtaal | |||||||||
2011-05-06 10:35 | elopio | Modules | => Core | |||||||||
2011-05-06 10:35 | elopio | OBNetwork customer | => No | |||||||||
2011-05-06 14:22 | hgbot | Checkin | ||||||||||
2011-05-06 14:22 | hgbot | Note Added: 0036511 | ||||||||||
2011-05-06 14:22 | hgbot | Status | new => resolved | |||||||||
2011-05-06 14:22 | hgbot | Resolution | open => fixed | |||||||||
2011-05-06 14:22 | hgbot | Fixed in SCM revision | => http://code.openbravo.com/erp/devel/pi/rev/ebead384d08cfd22bbd41c7d6d5bd75acef79bdc [^] | |||||||||
2011-05-11 08:46 | elopio | Relationship added | related to 0017109 | |||||||||
2011-05-11 08:57 | elopio | Tag Attached: testability | ||||||||||
2011-05-12 13:30 | hudsonbot | Checkin | ||||||||||
2011-05-12 13:30 | hudsonbot | Note Added: 0036845 | ||||||||||
2011-06-03 13:03 | iperdomo | Note Added: 0037962 | ||||||||||
2011-06-03 13:03 | iperdomo | Status | resolved => closed |
Notes | |||||
|
|||||
|
|
||||
|
|||||
|
|
||||
|
|||||
|
|