Damyon Wiese authored Apr 08, 2019 and Sara Arjona committed Apr 08, 2019

When output from javascript they should match what gets output from php.

Damyon Wiese authored Feb 11, 2019 and Sara Arjona committed Apr 08, 2019

Remove duplicate alt text from activity menu icons and the links to add new sections.

Added new target to predict which students are at risk of not getting
the minimum grade to pass a course.

Mathew May authored Apr 05, 2019 and Sara Arjona committed Apr 05, 2019

We found issues in FireFox where Behat could not scroll to select
the student two checkbox.

This change enhances security and avoid any kind of XSS attack.

* Unit tests for external functions
* Use the new dml_table to fetch a table's columns

Andrew Nicols authored Mar 19, 2016 and Peter Dias committed Apr 04, 2019

This patch adds new capabilities:
'mod/forum:postprivatereply'   - whether a user is able to post private replies; and
'mod/forum:readprivatereplies' - whether a user is able to read private replies.

Private replies are only visible to the intended recipient (the author of
the parent post), the author of the private reply, and those with the
ability to read private replies.

If a post is private then it cannot be replied to further.

By adding the "Search" aria label to a number of elements
any search of "Search" buttons, previously working in other
parts of the UI are not found anymore (because the hidden
ones are found before).

So, moving to click via xpath. Ideally we should be able to
find the target button in an easier, human readable way. But
there aren't many ids, names around to make it easier.

This is a followup of 85f47bae, where we were relaxing
the (new since phpunit 7.x) strict (===) isEqual()
comparison for strings. Copying the explanations for
easier understanding.

Link: https://github.com/sebastianbergmann/phpunit/issues/3185
Solution here is one of:
  a) Return to the previous situation, making the comparison
     softer. That can achieved by forcing different types, so
     float == string works.
  b) Changing APIs (both forms and database return strings) to
     perform some conversion to floats. That would make float
     comparison (with floats or strings) to work too.
The patch here follows the a) approach. Changing all the internals
for proper float handling sounds excesive when it has been working
perfectly since ever. So we went the easier route, just getting
rid of the new === comparisons when needed by changing expectation
types to float.