-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix #4076: Update end exploration (within collection) headers to better illustrate that the user should return to the collection #4130
Conversation
collection can be fully completed for testing purposes.
collection and to match the provided mocks.
with return to library text.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thanks! Planning to add any e2e tests to prevent regression?
I'm not opposed, but what did you have in mind? We don't currently have screendiff testing, and since this PR does not include functional changes I'm not sure what meaningful aspect of this change we would test. |
I think just checking that the correct text/items appear? Not so much in terms of layout/UI but that, e.g., as a logged out user coming to the end of an exp in a collection, the correct exp summary tile is recommended next and the correct link is shown below it. |
Hi @BenHenning -- e2e tests are failing persistently. Not exactly sure what's going on, but I'm going to restart them. If the failure persists, please could you take a look at it? Thanks! |
Backend tests are also failing. |
for the new strings that were added).
I fixed the backend test failures, but I have no clue yet why the protractor test is failing. |
There's apparently some jquery error being printed out on the collection viewer page:
Odd thing is, I didn't change anything related to that page in this PR. |
This seems to be an existing issue exposed by the changes to the example collection yaml file. This is probably an existing bug in the viewer that somehow wasn't hit before, and it's not yet clear what's actually broken. |
Note that hand-made collections don't seem to have this error in prod (e.g. https://www.oppia.org/collection/4UgTQUc1tala) |
This appears to be an error with the path generation in the collection player. Not yet clear why the new collection structure is causing this. |
Apparently the control points for the Bezier curve aren't being correctly computed when there are 3 nodes:
|
/cc @kevintab95 original code introduced in #2526 |
Does that happen with manually-created 3-node collections as well? I'm surprised we haven't run into that problem before in practice. |
Haven't checked, but I'm working around this by adding a 4th test exploration to the demo collection. We can follow up with this issue separately. |
Yes, this does repro with a manually-created 3-node collection as well. |
Issues fixed & repushed. Waiting on Travis now. PTAL since there are a few new things that have been changed. |
Codecov Report
@@ Coverage Diff @@
## develop #4130 +/- ##
========================================
Coverage 43.88% 43.88%
========================================
Files 360 359 -1
Lines 22401 22401
Branches 3559 3559
========================================
Hits 9831 9831
Misses 12570 12570
Continue to review full report at Codecov.
|
@@ -129,60 +129,58 @@ def test_welcome_collection(self): | |||
self.assertEqual( | |||
collection_dict['title'], 'Introduction to Collections in Oppia') | |||
|
|||
# Verify there are 5 explorations in this collection, the initial | |||
# Verify there are 3 explorations in this collection, the initial |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
4?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ugh, I had updated this once and missed it the second time. :( Done.
core/tests/protractor/collections.js
Outdated
@@ -33,8 +33,6 @@ describe('Collections', function() { | |||
adminPage.get(); | |||
adminPage.reloadCollection(); | |||
general.acceptAlert(); | |||
browser.waitForAngular(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This was just removed because it wasn't necessary? (Or was there some other reason?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wasn't necessary; reloading a collection automatically reloads the explorations it refers to (otherwise there would be a load error).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Apparently this is necessary for the collection editor test. :) I didn't read through it carefully enough, and since I was testing the player test in isolation I didn't realize removing this lines broke the other test.
Hi @BenHenning -- e2e tests still failing, unfortunately! |
Odd, it passed locally when I tried it yesterday. Will look into this. |
Fixed--readded the setup line to load all explorations. |
Thanks! Still LGTM. |
New behavior:
When ending an exploration within the context of a collection:
When ending an exploration outside the context of a collection:
Changes illustrated in text form:
Note: This also updates the demo collection to be a bit more usable in testing scenarios (and adds 2 new simple explorations specifically for that purpose).
Note2: FYI that #4131 is tracking the incorrect globe placement; that doesn't seem to have been caused by these changes.