tests/lib/lib.status - Issue 10197008: - Add tests/lib to start testing libraries outside of core.

Side by Side Diff

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Side by Side Diff: tests/lib/lib.status

Issue 10197008: - Add tests/lib to start testing libraries outside of core. (Closed) Base URL: http://dart.googlecode.com/svn/branches/bleeding_edge/dart/

Patch Set: Created 8 years, 8 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

OLD	NEW
(Empty)
	1 # Copyright (c) 2012, the Dart project authors. Please see the AUTHORS file

	2 # for details. All rights reserved. Use of this source code is governed by a

	3 # BSD-style license that can be found in the LICENSE file.
	Bill Hesse 2012/04/25 10:19:35 Tests are now supposed to end in _tests.dart, if t Tests are now supposed to end in _tests.dart, if they follow the standard that creates them with StandardTestSuite.forDirectory(dir). Consider doing this, and the change in test.dart.
	4

	5

	6 [ $compiler == dartc \|\| $compiler == frog \|\| $compiler == dart2js]
	Mads Ager (google) 2012/04/24 18:04:35 This really shouldn't be neccesary, right? In prin This really shouldn't be neccesary, right? In principle, the Dart code should work fine when translated to JavaScript since everything is operating on 32-bit integers. Ivan Posva 2012/04/25 09:14:01 It should not be necessary, but a quick test did n Show quoted text On 2012/04/24 18:04:35, Mads Ager wrote: > This really shouldn't be neccesary, right? In principle, the Dart code should > work fine when translated to JavaScript since everything is operating on 32-bit > integers. It should not be necessary, but a quick test did not succeed, so I disabled them to get this in while avoiding a red bot. Mads Ager (google) 2012/04/25 09:31:13 OK, let's file a bug and we should see if we can m Show quoted text On 2012/04/25 09:14:01, Ivan Posva wrote: > On 2012/04/24 18:04:35, Mads Ager wrote: > > This really shouldn't be neccesary, right? In principle, the Dart code should > > work fine when translated to JavaScript since everything is operating on > 32-bit > > integers. > > It should not be necessary, but a quick test did not succeed, so I disabled them > to get this in while avoiding a red bot. OK, let's file a bug and we should see if we can make it work when compiled to JS as well.
	7 *: Skip

	8

	9 [ $arch == arm ]

	10 *: Skip

	11

	12 [ $arch == simarm ]

	13 *: Skip

OLD	NEW

« no previous file with comments | « no previous file | tests/lib/src/crypto/sha1Test.dart » ('j') | tests/lib/src/crypto/sha1Test.dart » ('J')