[MGNLCE-267] Create UI test for export action Created: 18/May/18  Updated: 11/Mar/21

Status: Open
Project: Community Edition
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Leah Staniorski Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relation
is related to MAGNOLIA-7310 XML Exports open directly in browser ... Closed
is related to MGNLCE-269 Create UI test for download of file n... Accepted
Template:
Acceptance criteria:
Empty
Task DoR:
Empty
Date of First Response:

 Description   

Create export action UI test to make sure that it is working appropriately for file name's with special characters. The test should also check that the exported file is being downloaded by the browser instead of opened by the browser.



 Comments   
Comment by Roman Kovařík [ 08/Mar/21 ]

cmeier, do we have something like this?

Comment by Christoph Meier [ 08/Mar/21 ]

rkovarik - as far as I know - we don't have (yet).

Comment by Christoph Meier [ 08/Mar/21 ]

Hi lstaniorski, I have a few questions.


(a) Exported files = bootstrap files (.xml or .yaml) only? ... or "anything" else?

 


(b) Filenames with special characters.
Here I'm, really not sure what your expectations are. The way Magnolia specifies the node name - which will go into the filename of the exportable - is a bit "rude".
Examples

Page name Node name Exportable file name
Bäärchen B--rchen website.B--rchen.yaml
Люблю
website.-----.yaml
йохен
website.-----.yaml
chèvre ch-vre website.ch-vre.yaml

Is that what yo expect and consider as correct?


(c) If doable - and if we don't do this already - should we force the download?

Generated at Mon Feb 12 00:07:45 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.