| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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.
|
|
a read-only conditional prior to the item search within three functions that search for an item index in the TList prior to editing.
|
|
are conditionals for 3.3 and 3.4. No more Framework file includes are needed with 3.5.
|
|
things done a touch. This also updates the unit test. The unit test isn't perfect just yet but this class works 100% as a TList. As things get settled I'll get the docs going on this new class.
|
|
Adds the Unit test. TPriorityList needs more unit testing but I wanted to submit this so the method names can be peer reviewed.
|
|
TList::insertAfter using the unit test.
|
|
|
|
|
