Inline text files in unit tests
Review Request #9971 — Created May 23, 2018 and submitted
Instead of the base test case opening and closing the same files
multiple times we have now moved the files inline with the code
resulting in a lower time complexity and a more streamline code design.
Re-ran the unit tests to make sure they behaved as expected.
Description | From | Last Updated |
---|---|---|
Can you delete the files you inlined? There is no reason to keep them in the repository. |
brennie | |
Testing done -- did you run unit tests? :) |
brennie | |
Can you wrap your description at 72 instead of (what I assume is) 52? |
brennie | |
Extra space in your change description: "we have now<2 spaces>moved the files ..." |
chipx86 | |
Can you suffix all these with _DIFF ? |
brennie | |
Can you extract this into a variable like the others? |
brennie | |
Can you pull this out into a variable and do {'path': diff} ? |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
Same here. |
brennie | |
You can set diff= as a parameter to Commit. |
chipx86 | |
You can set diff= as a parameter to Commit. |
chipx86 | |
It's best not to change lines that aren't related to the changes in the file. Makes it hard to go … |
chipx86 | |
While nice, this cleanup also doesn't belong in this change. |
chipx86 | |
We have a lot of variations in how we're creating this. Can you go through the change and make sure … |
chipx86 |
- Description:
-
~ Instead of the base test case opening and closing the
~ same files multiple times we have now moved the files ~ inline with the code resulting in a lower time ~ Instead of the base test case opening and closing the same files
~ multiple times we have now moved the files inline with the code ~ resulting in a lower time complexity and a more streamline code design. - complexity and a more streamline code design. - Testing Done:
-
+ Re-ran the unit tests to make sure they behaved as expected.
- Commit:
-
d6a37d23a768ca6b5ef4882b3c5823d0d9e3bbd3135505a7e7d39395aec4c21ce686d130571f71da
- Diff:
-
Revision 2 (+339 -327)
Checks run (1 succeeded, 1 failed with error)
- Commit:
-
135505a7e7d39395aec4c21ce686d130571f71dafa2d3276dbed70edfe2141b01dae03451c93aab7
- Diff:
-
Revision 3 (+340 -327)
Checks run (1 succeeded, 1 failed with error)
-
-
-
-
-
It's best not to change lines that aren't related to the changes in the file. Makes it hard to go through the history of code later ("I wanted to see when this docstring was added -- why was it changed in this change??"). Can you revert the docstring/line wrapping changes?
-
-
We have a lot of variations in how we're creating this. Can you go through the change and make sure we always pull out
diff = SimpleUploadedFile
so it's explicitly done separately from the post operation?
- Description:
-
Instead of the base test case opening and closing the same files
~ multiple times we have now moved the files inline with the code ~ multiple times we have now moved the files inline with the code resulting in a lower time complexity and a more streamline code design. - Commit:
-
fa2d3276dbed70edfe2141b01dae03451c93aab738d669b86344afeb87ebc6f30d2bd07244d687ec
- Diff:
-
Revision 4 (+310 -292)