| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2010-11-10 | scenario repeater should match only visible stuff | Igor Minar | |
| 2010-11-09 | Support substring matching of bindings with repeater(). Closes #123 | Elliott Sprehn | |
| 2010-11-02 | Provide better sandbox error messages, and disallow running from file:// URLs | Elliott Sprehn | |
| 2010-10-29 | Check if file exists (not a 404) and that document is accessible and not ↵ | Elliott Sprehn | |
| using file:// URLs in Application | |||
| 2010-10-26 | fixes IE related failures, and form submit event handling in ie | Misko Hevery | |
| 2010-10-26 | Lots of bug fixes in the scenario runner and a bunch of new features. | Elliott Sprehn | |
| - By default the runner now creates multiple output formats as it runs. Nodes are created in the DOM with ids: json, xml, and html. ex. $('#json').html() => json output of the runner ex. $('#xml').html() => json output of the runner $result is also an object tree result. The permitted formats are html,json,xml,object. If you don't want certain formats you can select specific ones with the new ng:scenario-output attribute on the script tag. <script src="angular-scenario.js" ng:scenario-output="xml,json"> - Added element(...).count() that returns the number of matching elements for the selector. - repeater(...).count() now returns 0 if no elements matched which can be used to check if a repeater is empty. - Added toBe() matcher that does strict equality with === - Implement iit and ddescribe. If iit() is used instead of it() then only that test will run. If ddescribe() is used instead of describe() them only it() statements inside of it will run. Several iit/ddescribe() blocks can be used to run isolated tests. - Implement new event based model for SpecRunner. You can now listen for events in the runner. This is useful for writing your own UI or connecting a remote process (ex. WebDriver). Event callbacks execute on the Runner instance. Events, if fired, will always be in the below order. All events always happen except for Failure and Error events which only happen in error conditions. Events: RunnerBegin SpecBegin(spec) StepBegin(spec, step) StepError(spec, step, error) StepFailure(spec, step, error) StepEnd(spec, step) SpecError(spec, step, error) SpecEnd(spec) RunnerEnd - Only allow the browser to repaint every 10 steps. Cuts 700ms off Firefox in benchmark, 200ms off Chrome. - Bug Fix: Manually navigate anchors on click since trigger wont work in Firefox. | |||
| 2010-10-22 | Workaround for http://bugs.jquery.com/ticket/7292 | Misko Hevery | |
| 2010-10-22 | Horrible IE + jQuery hack to make the tests pass | Misko Hevery | |
| 2010-10-22 | fixed issue with ie .data() method failing tests | Misko Hevery | |
| 2010-10-20 | fix some of the failing ie tests | Misko Hevery | |
| 2010-10-20 | Lots of stability and performance updates and UI polish too. | Elliott Sprehn | |
| Polish the Scenario Runner UI to include: - a scroll pane that steps appear in since the list can be very long - Collapse successful tests - Show the line where the DSL statements were when there's an error (Chrome, Firefox) Also: - Remove lots angular.bind calls to reduce the amount of stack space used. - Use setTimeout(...,0) to schedule the next future to let the browser breathe and have it repaint the steps. Also prevents overflowing the stack when an it() creates many futures. - Run afterEach() handlers even if the it() block fails. - Make navigateTo() take a function as the second argument so you can compute a URL in the future. - Add wait() DSL statement to allow interactive debugging of tests. - Allow custom jQuery selectors with element(...).query(fn) DSL statement. Known Issues: - All afterEach() handlers run even if a beforeEach() handler fails. Only after handlers for the same level as the failure and above should run. | |||
| 2010-10-19 | fixed Scenario.js so that it does not clobber global vars | Misko Hevery | |
| 2010-10-19 | fixed tests | Misko Hevery | |
| 2010-10-19 | Fix browser triggering in scenario to always do native events. | Misko Hevery | |
| - Also fixed angular.suffix for scenarios - refactored click() to browserTrigger() - Fixed Rakefile with CSS and jQuery | |||
| 2010-10-14 | New Angular Scenario runner and DSL system with redesigned HTML UI. | Elliott Sprehn | |
| Uses the Jasmine syntax for tests, ex: describe('widgets', function() { it('should verify that basic widgets work', function(){ navigateTo('widgets.html'); input('text.basic').enter('Carlos'); expect(binding('text.basic')).toEqual('Carlos'); input('text.basic').enter('Carlos Santana'); expect(binding('text.basic')).not().toEqual('Carlos Boozer'); input('text.password').enter('secret'); expect(binding('text.password')).toEqual('secret'); expect(binding('text.hidden')).toEqual('hiddenValue'); expect(binding('gender')).toEqual('male'); input('gender').select('female'); expect(binding('gender')).toEqual('female'); }); }); Note: To create new UI's implement the interface shown in angular.scenario.ui.Html. | |||
 |
index : angular.js | |
| aboutsummaryrefslogtreecommitdiffstats |