Reorganize "Testing" pages
Created by: totten
Based on the evaluation/planning at the Devon sprint, we felt it was important to provide a better framing/summary of the kinds of tests that are available (and when to use them).
This PR reorganizes the content of the "Testing" chapter, migrates in content from civicrm-core READMEs, and opens with a table to visualize the choice of testing techniques.
It's planned to put Codeception and Protractor in here as well, but the for the moment I've disabled those links.
(Comment updated Oct 30.)
Merge request reports
Merged by
(Apr 6, 2025 9:01am UTC)
Activity
Created by: seancolsen
@totten What's the status of this PR? Still WIP? What else does it need? I haven't looked at it yet. Just trying to whittle down the PR queue atm.
-
Created by: totten
@seanmadsen I think this is a mergeable revision now.
In the summary table, I'm a little on the fence about whether to include the "Trade off" and "Good for" blurbs. Showing them makes the table a better summary; but hiding them makes the table a bit more approachable.
- Last reply by homotechsual
- Last reply by homotechsual
- Last reply by homotechsual
- Last reply by homotechsual
- Last reply by homotechsual
1 1 Documentation+Infrastructure+Canary develop 2 2 Book+style+guide best-practices/documentation-style-guide 3 CiviCRM+Unit+Testing+basic+information testing/setup -
Created by: totten
I'm taking this as a lesson in Github mechanics -- when there's a line edit (removal+addition), you can comment on either the removal or the addition. It seems better to comment on the addition -- because (in that case) Github will automatically recognize that the code-review has been addressed.
1 1 Documentation+Infrastructure+Canary develop 2 2 Book+style+guide best-practices/documentation-style-guide 3 CiviCRM+Unit+Testing+basic+information testing/setup