Test coverage for editing a translation

when translating: no add or remove buttons on the paragraphs are present

That is more or less by design. But the effect it has on deleting is definitely not intendted.

See also this issue that explains the situation / limitation: #2461695: Support asymmetric translations

From the README.txt:

- Make sure that the content type with a paragraph field is set to NOT translatable.
- Set the fields of each paragraph type to translatable as required.

Chances are you don't want to do what you did.
If you fix the setup, is the bug still pending?

Back to active then. Will check, provide feedback, fix.

Can reproduce. That's a critical thing indeed.
(Pretty sure this worked once.)
Let's start with extending a test and then identify and fix the issue...

This is a core bug. This is an opened issue to fix it.

The core issue was fixed, which should have fixed this.

We still want test for this, however so changing to a task.

Uploaded patch for issue #2527644:

• added test coverage for saving the original paragraph article on second request

I think we just need to extend the existing test (testParagraphTranslation()), not add a new one for that, since this adds lots of loading time to our test.
It should be as easy as two lines of code at the end. :)

Uploaded patch:

• modified testParagraphTranslation() adding the saving command for the original content on second request :)

1. +++ b/src/Tests/ParagraphsTranslationTest.php
   @@ -120,5 +120,12 @@ class ParagraphsTranslationTest extends WebTestBase {
   +    // Save the original content on second request
   

   Missing dot at the end of the sentence.

2. +++ b/src/Tests/ParagraphsTranslationTest.php
   @@ -120,5 +120,12 @@ class ParagraphsTranslationTest extends WebTestBase {
   +    $this->assertNoText('The content has either been modified by another user,
   +        or you have already submitted modifications.
   +        As a result, your changes cannot be saved.');
   

   No need for line breaks. You can write one sentence after another, and limit the line to 80 chars.

Also, don't forget to post interdiffs.

Are we sure that assertNoText works correctly with the line breaks?

I think testing for "The content has either been modified by another user" is perfectly enough.
(But i think it's a redundant check to the "...has been updated." and could be omitted if we check for success explicitly..)

Hmm, I checked... It doesn't work correctly with line breaks.

Uploaded patch:

• added dot at the end of the sentence :)
• dropped last assertNoText()

Yes, I also have checked the line break thing and yes, it does not work!

Not sure if we need the assertNoText() or not. But without is fine for me.

To be consistent with the whole method testParagraphTranslation(), we may need also the last assertNoText() as well, since also for // Check the english translation. and // Check the french translation. we do have double checks.
But I also find it a bit redundant (if we successfuly saved the paragraph then the assertNoText() will always pass as well).

Thanks, pushed to dev!