Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Fix issue with bad updates causing disappearing tests #464
Conversation
|
Thank you! |
|
Still not working on https://jsperf.com/arr-map-filter-reduce/4/edit - Only my added test is inserted and the others are lost, even when updated. |
|
I'm having the same issue, editing a test suite and not having the exisiting tests added, for this suite https://jsperf.com/preallocating-array |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Fixes #236
Pretty much similar to #414, but with an added test to show the issue.
Based on what @mathiasbynens said in that PR #414 (comment)
It seems like the original fix in #414 was correct. I have also written a test that shows the correct action.
If you are the owner of the test (aka you own the 1st revision), only you (with the
isOwnflag set to true) should be able to "update" an existing test. Otherwise you are not the owner and you should only be inserting your test cases into a revision.The reason for all the tests having "empty" test cases is because the code would fall into the UPDATE sql statement every single time regardless of whether you're the actual owner or not because each test always passes a testID unless a new test case is added to your revision of the test.
E.g. every test has the two basic test cases, and so if you try to create a new revision and only edit those 2 test cases, you'll get a blank test revision. If you add an extra test case in that revision, then that one won't have a
testIDand thus will make an INSERT call and this new revision will only have the new test case.The additional test case shows that if you are the owner, you make updates if the test cases exist, and if you are not the owner you only make inserts.