I @skip'd the functional tests for adding new compendium entries in 2c50f5bbc686985544c3b329959321d9de04697d due to some critical changes in how the form was being rendered on the site. In particular, it's currently possible to write the abstract as Markdown using UIkit's HTML/Markdown editor component, which allows us to offer much richer views at the expense of some additional complexity. The functional tests fail now because CodeMirror and marked replace the old <textarea>...</textarea> with a Markdown editor. We can't just have Selenium search for #id_abstract and execute send_keys anymore.
This is a fairly important component of the site to have functional tests for since it's very JavaScript-dependent. Eventually we need to re-implement functional tests so that we can ensure that the new entry form works correctly in practice.
I
@skip'd the functional tests for adding new compendium entries in 2c50f5bbc686985544c3b329959321d9de04697d due to some critical changes in how the form was being rendered on the site. In particular, it's currently possible to write the abstract as Markdown using UIkit's HTML/Markdown editor component, which allows us to offer much richer views at the expense of some additional complexity. The functional tests fail now because CodeMirror and marked replace the old<textarea>...</textarea>with a Markdown editor. We can't just have Selenium search for#id_abstractand executesend_keysanymore.This is a fairly important component of the site to have functional tests for since it's very JavaScript-dependent. Eventually we need to re-implement functional tests so that we can ensure that the new entry form works correctly in practice.