| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | 1134 | Kartik K. Agaram | 2015-04-22 | 1 | -23/+23 |
| | | |||||
| * | 1133 - more reorg of commandline parsing | Kartik K. Agaram | 2015-04-22 | 1 | -17/+2 |
| | | | | | | | | | | | | | | | | | | | | | | | 1. Drop the ability to run just some C++ tests. It's a lousy interface to use line numbers, we can't selectively run mu tests, we haven't used it in a while because our tests run plenty fast, and it's complicating other parts, like Next_recipe_number and test space handling. 2. Create a new layer right up top to show the usage message and all the different forms that are possible. Good for documentation until we come up with a way to put the different forms in their own layers. At least it's out of the test layer now. 3. Strengthen the assertion that no recipes exist in test space before we start running any sorts of tests. Earlier it was possible for files loaded explicitly to overflow into test space because we were asserting before load, not after. Now we check if we need to run tests, load all files, then make the assertion, run tests, and exit if necessary. Now we don't need to mess with commandline args at all in layer 50. That's a sign that we're on the right track. | ||||
| * | 1128 | Kartik K. Agaram | 2015-04-22 | 1 | -1/+0 |
| | | | | | | | Reorganized commandline handling to perform test space assertion in just one place at the right layer. Hopefully this issue will not bite us again. | ||||
| * | 1127 | Kartik K. Agaram | 2015-04-22 | 1 | -1/+1 |
| | | | | | | | | | | | Move assertions about test space right before running all tests. (But not before running *every* test.) This is a good trip-wire, but it requires that we remember to set it in any new code paths running tests. Still one wart: layer 1 depends on layer 10. | ||||
| * | 1126 - 'mu test x.mu' runs just scenarios in x.mu | Kartik K. Agaram | 2015-04-22 | 1 | -21/+54 |
| | | | | | | | | Required still more tweaking of Recipe namespaces. Mindlessly inserting setup() took a couple of hours to debug because the test function and the function it was testing ended up getting the same recipe number, with the inevitable infinite loop :/ | ||||
| * | 1116 - simpler memory checks | Kartik K. Agaram | 2015-04-20 | 1 | -1/+32 |
| | | |||||
| * | 1110 - 'scenarios' directive applies only to current file | Kartik K. Agaram | 2015-04-20 | 1 | -2/+0 |
| | | |||||
| * | 1108 - check for typos in memory expectations in scenarios | Kartik K. Agaram | 2015-04-20 | 1 | -0/+15 |
| | | |||||
| * | 1107 | Kartik K. Agaram | 2015-04-20 | 1 | -1/+46 |
| | | |||||
| * | 1104 - support 'dump' in mu scenarios | Kartik K. Agaram | 2015-04-19 | 1 | -4/+7 |
| | | |||||
| * | 1091 | Kartik K. Agaram | 2015-04-17 | 1 | -14/+0 |
| | | |||||
| * | 1090 | Kartik K. Agaram | 2015-04-17 | 1 | -1/+1 |
| | | |||||
| * | 1088 - start porting the 'buffer' type | Kartik K. Agaram | 2015-04-17 | 1 | -1/+4 |
| | | |||||
| * | 1077 | Kartik K. Agaram | 2015-04-17 | 1 | -0/+1 |
| | | |||||
| * | 1075 | Kartik K. Agaram | 2015-04-17 | 1 | -0/+132 |