| Age | Commit message (Collapse) | Author |
|---|
|
compatibility layer
(cherry picked from commit 82774aa0a41562a325f31c901584ec01c8238573)
Conflicts:
tests/FunctionalTests/active-controls/tests/AutoCompleteTestCase.php
tests/FunctionalTests/active-controls/tests/CustomTemplateTestCase.php
tests/FunctionalTests/tickets/tests/Ticket220TestCase.php
tests/FunctionalTests/tickets/tests/Ticket719TestCase.php
tests/FunctionalTests/tickets/tests/Ticket769TestCase.php
tests/FunctionalTests/validators/tests/DataTypeValidatorTestCase.php
|
|
browser's quirks mode
(cherry picked from commit a0d6864093cf13a96dafa8a47b5c43891b2b864f)
Conflicts:
tests/FunctionalTests/active-controls/protected/pages/ActivePanelTest.page
tests/FunctionalTests/active-controls/protected/pages/PostLoadingTest.page
|
|
(cherry picked from commit b340ed9cc57f327785ebc0c1b8fb725ffb02d647)
|
|
(cherry picked from commit ae7a187ec50d2a4d68fc9b22acf7d46660eca402)
|
|
(cherry picked from commit 410af66fc8843177bb68561e556d7bd51c4d71c1)
Conflicts:
tests/FunctionalTests/tickets/tests/Ticket769TestCase.php
|
|
Any browser’s development tool is way better, and it stops exceptions
from being catched by the browser’s console
(cherry picked from commit 0a136fe37491281ada5084b6eb5a72d4ca8d948a)
|
|
with git
(cherry picked from commit 3e9969766153839abfb7de59e0c778a604bfbf55)
Conflicts:
framework/Web/UI/ActiveControls/TCallbackClientScript.php
framework/Web/UI/JuiControls/TJuiAutoComplete.php
framework/Web/UI/JuiControls/TJuiControlAdapter.php
framework/Web/UI/JuiControls/TJuiDraggable.php
framework/Web/UI/JuiControls/TJuiDroppable.php
framework/Web/UI/JuiControls/TJuiResizable.php
framework/Web/UI/JuiControls/TJuiSelectable.php
framework/Web/UI/JuiControls/TJuiSortable.php
|
|
(cherry picked from commit 5d9f6fc77131d75e6c73a7e57df8d967b6b09215)
Conflicts:
tests/FunctionalTests/validators/tests/DatePickerTestCase.php
|
|
|
|
the tests using keyDown() had to be commented out..
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Functional tests were using an old selenium RC version. Ported them to
use phpunit + selenium; next: opensauce
|
|
TComponent Update: Behaviors, Class Behaviors, fx global events, and dy
one to one events.
This patchset was currently available only on svn trunk/
|
|
|
|
testcases. Fixes #486
|
|
|
|
|
|
|
|
|
|
Otherwise git would strip them away
|
|
apps; gitignore only their contents
The directories needs to exists in order for demos and tests to run
correctly
|
|
|
|
|
|
|
|
|
|
what seems a test suite for an older version of SQLMap)
|
|
- it will use the system PHPUnit installation if available (bundled PHPUnit with prado is no more a choice)
- fixed tests in order to be compatible with recent phpunit versions (currently 3.7)
- dropped old tests referring to unexisting components (NOTE: this includes what seems a test suite for an older version of SQLMap)
Added some svn-ignore properties
|
|
This adds global 'fx' events, behaviors, class-wide behaviors, intra-object/behavior 'dy' events, and tweaks the raiseEvent to be more advanced (yet backward compatible). A large amount of documentation is in here too. Slight changes to the TApplication object is made to provide events with priorities. TComponent has a massive amount of test cases as well… There are now 512 assertions. Test cases have been added for testing the GetJS and SetJS and ensure functionality of these new getters and setters.
The Behaviors are all tested and fully integrated into the TComponent Object. Behaviors are more transparently and widely integrated into TComponent.
Class Behaviors rely on the global events to add behaviors to instanced objects. Class behaviors also allow for behaviors to be added during the instancing of new objects of the class.
Dynamic events enable the object to send events directly to behaviors as intra-object events. Dynamic events can be chained as multiple behaviors may implement the event. This allows for parameter filtering.
RaiseEvent allows for raising global events, capturing results, and feeding results forward into the next handlers parameters should the need arise. This is a forward thinking feature to enable new processes to be designed into the code for PRADO version 3.3 and future version 4.0. This functionality is transparent when unused.
We are hoping this is fully backward compatible with the existing code base. It was designed for maximum backward compatibility while expanding the functional base exponentially.
This clears the way for a new way of thinking about how objects relate.
|
|
|
|
|
|
activecontrol, set its style to display:none to ensure it's considered not-visible by clientside javascript
|
|
Fixed ActiveDropDownListtestCase, added a dummy selenium.css to avoid a 404 error while debugging test cases
|
|
|
|
the fix of #91
|
|
a quickstart example, updated 2 tests that were broken + HISTORY
|
|
TSecurityManagerTest: loop through different string length to take account of mcrypt's block cipher padding
TAPCCacheTest: fixed static member usage
THttpRequestTest: fixed testRequestWithUrlMapping test
|
|
below a specific priority, with inclusion. Added TPriorityMap and test cases.
|
|
|
|
|
|
version of TinyMCE; small fix for unittest ticket#439
|
|
|
|
if InputMode="DropDownList" )
Testcase for ActiveDatePicker have been updated (it was checking for year 2005 in the datepicker, now it checks for date('Y')+1)
|
|
|
|
function removal.
|
|
missing unit test to TList.
|
