about summary refs log tree commit diff stats
path: root/002test.cc
Commit message (Collapse)AuthorAgeFilesLines
* 3907 - standardize test failure messagesKartik K. Agaram2017-06-151-1/+1
|
* 3749Kartik K. Agaram2017-03-021-1/+1
|
* 3561Kartik K. Agaram2016-10-221-1/+1
|
* 3558Kartik K. Agaram2016-10-221-5/+5
|
* 3557Kartik K. Agaram2016-10-221-1/+1
|
* 3532Kartik K. Agaram2016-10-201-2/+1
| | | | Coalesce all the management of number of failed scenarios.
* 3522Kartik K. Agaram2016-10-191-2/+2
|
* 3433Kartik K. Agaram2016-10-011-1/+1
|
* 3291Kartik K. Agaram2016-09-021-2/+2
| | | | Stop double-counting failing tests in some situations.
* 3273Kartik K. Agaram2016-08-281-1/+2
| | | | | | | | | | | Undo 3272. The trouble with creating a new section for constants is that there's no good place to order it since constants can be initialized using globals as well as vice versa. And I don't want to add constraints disallowing either side. Instead, a new plan: always declare constants in the Globals section using 'extern const' rather than just 'const', since otherwise constants implicitly have internal linkage (http://stackoverflow.com/questions/14894698/why-does-extern-const-int-n-not-work-as-expected)
* 3272Kartik K. Agaram2016-08-281-2/+1
| | | | | | Move global constants into their own section since we seem to be having trouble linking in 'extern const' variables when manually cleaving mu.cc into separate compilation units.
* 3270Kartik K. Agaram2016-08-281-2/+4
| | | | | | | | | | | | Clean up the Globals section so that we can generate extern declarations for all globals out using this command after we carve it out into globals.cc: grep ';' globals.cc |perl -pwe 's/[=(].*/;/' |perl -pwe 's/^[^\/# ]/extern $&/' > globals.h The first perl command strips out initializers. The second prepends 'extern'. This simplistic approach requires each global definition to lie all on one line.
* 3177Kartik K. Agaram2016-08-131-1/+1
| | | | Systematize all the newlines while displaying test progress.
* 3165Kartik K. Agaram2016-08-101-1/+1
|
* 3027Kartik K. Agaram2016-06-021-1/+1
|
* 2773 - switch to 'int'Kartik K. Agaram2016-03-131-2/+2
| | | | This should eradicate the issue of 2771.
* 2700 - fail tests on unexpected errors or warningsKartik K. Agaram2016-02-251-1/+2
|
* 2697Kartik K. Agaram2016-02-241-3/+3
|
* 2095Kartik K. Agaram2015-08-281-1/+1
| | | | | | | | | | | | Finally terminate the experiment of keeping debug prints around. I'm also going to give up on maintaining counts. What we really need is two kinds of tracing: a) For tests, just the domain-specific facts, organized by labels. b) For debugging, just transient dumps to stdout. b) only works if stdout is clean by default. Hmm, I think this means 'stash' should be the transient kind of trace.
* 1965 - don't die on '-' ingredientKartik K. Agaram2015-08-101-1/+13
| | | | Thanks Caleb Couch.
* 1641Kartik K. Agaram2015-06-241-1/+1
| | | | | | Snapshot in switching editor-data.cursor to editor-data.before-cursor. But I have trouble coercing events to touch events, even though using the integer tag 2 for the conversion works.
* 1474 - another warningKartik K. Agaram2015-05-261-0/+1
|
* 1437Kartik K. Agaram2015-05-231-1/+1
|
* 1434 - support all unicode spacesKartik K. Agaram2015-05-231-0/+1
|
* 1391 - avoid unsigned integersKartik K. Agaram2015-05-171-3/+3
|
* 1389Kartik K. Agaram2015-05-161-1/+1
|
* 1388Kartik K. Agaram2015-05-161-0/+1
|
* 1387Kartik K. Agaram2015-05-161-3/+3
|
* 1358 - inform shell of test failureKartik K. Agaram2015-05-121-1/+3
|
* 1357 - temporarily revert floating-point supportKartik K. Agaram2015-05-121-1/+0
|
* 1356 - snapshot #2: floating point supportKartik K. Agaram2015-05-121-0/+1
| | | | | | | | | | | | | | | I added one test to check that divide can return a float, then hacked at the rippling failures across the entire entire codebase until all tests pass. Now I need to look at the changes I made and see if there's a system to them, identify other places that I missed, and figure out the best way to cover all cases. I also need to show real rather than encoded values in the traces, but I can't use value() inside reagent methods because of the name clash with the member variable. So let's take a snapshot before we attempt any refactoring. This was non-trivial to get right. Even if I convince myself that I've gotten it right, I might back this all out if I can't easily *persuade others* that I've gotten it right.
* 1354Kartik K. Agaram2015-05-121-2/+2
|
* 1343Kartik K. Agaram2015-05-111-1/+1
|
* 1276 - make C++ version the defaultKartik K. Agaram2015-05-051-0/+93
I've tried to update the Readme, but there are at least a couple of issues.