small change to test #2301

[robertoostenveld]

No description provided.

[github-actions]

You should test whether your modifications do not break anything.
See https://www.fieldtriptoolbox.org/development/testing/

When outside the DCCN, please consider testing: test_tutorial_beamformer20131122, test_issue1198, test_bug3029, test_tutorial_coherence, test_tutorial_beamformingextended, test_bug1599, test_tutorial_beamformingextended20131122, test_bug1976, test_beamformer_sam, test_bug1563, test_tutorial_meguk2015, test_tutorial_beamformer, test_tutorial_beamformer20120321, inspect_ft_sourcemovie, test_bug2664, test_pull1377b, test_pull1377, test_ft_sourceanalysis, test_bug3124, test_bug3078, test_shared_virtual_channels, test_tutorial_connectivity3

When inside the DCCN, please also consider testing: test_bug2399, test_bug2834, test_bug1049, test_bug1746, test_pull1377, test_beamformer_whitening, test_tutorial_meguk2015, test_prepare_freq_matrices, test_bug2959, test_bug1298, test_bug2005, test_pull1456, test_pull1663, test_bug3029, test_pull1377b

Suggested tests outside the DCCN use public data or do not use data.
Suggested tests inside the DCCN use private data.

[robertoostenveld]

whohoo!!!

It works.

[robertoostenveld]

It would be nice to reformat the output a bit, such that it is easier to copy-and-paste the test scripts into MATLAB. Something that would work nicely is

edit test_001 test_002 test_003

which allows a quick inspection of the test script prior to clicking the "run" button to execute each of the scripts.

Also, since the comment is formatted in Markdown, we can use a code block to distinguish the part to be evaluated in MATLAB from the explanation.

[github-actions]

You should test whether your modifications do not break anything.
See https://www.fieldtriptoolbox.org/development/testing/

When outside the DCCN, please consider testing: test_bug2664, inspect_ft_sourcemovie, test_tutorial_coherence, test_tutorial_beamformingextended, test_bug1599, test_bug1976, test_tutorial_connectivity3, test_bug3124, test_ft_sourceanalysis, test_bug3029, test_tutorial_meguk2015, test_pull1377, test_shared_virtual_channels, test_tutorial_beamformer, test_tutorial_beamformer20131122, test_issue1198, test_pull1377b, test_tutorial_beamformer20120321, test_bug1563, test_beamformer_sam, test_tutorial_beamformingextended20131122, test_bug3078

When inside the DCCN, please also consider testing: test_bug1746, test_bug2399, test_bug1049, test_prepare_freq_matrices, test_bug2005, test_beamformer_whitening, test_bug3029, test_pull1456, test_bug2959, test_pull1377b, test_bug2834, test_bug1298, test_tutorial_meguk2015, test_pull1377, test_pull1663

Suggested tests outside the DCCN use public data or do not use data.
Suggested tests inside the DCCN use private data.

[github-actions]

You should test whether your modifications do not break anything.
See https://www.fieldtriptoolbox.org/development/testing/

When outside the DCCN, please consider testing: test_tutorial_beamformer20120321, test_tutorial_beamformer20131122, test_bug1976, test_bug1563, test_bug3124, test_tutorial_connectivity3, test_beamformer_sam, test_pull1377b, inspect_ft_sourcemovie, test_tutorial_beamformer, test_bug3078, test_tutorial_coherence, test_bug3029, test_pull1377, test_bug2664, test_shared_virtual_channels, test_issue1198, test_tutorial_beamformingextended, test_bug1599, test_tutorial_meguk2015, test_tutorial_beamformingextended20131122, test_ft_sourceanalysis

When inside the DCCN, please also consider testing: test_bug2834, test_bug3029, test_pull1377, test_bug2005, test_bug1298, test_bug2959, test_prepare_freq_matrices, test_tutorial_meguk2015, test_pull1663, test_bug1746, test_pull1377b, test_bug1049, test_pull1456, test_bug2399, test_beamformer_whitening

Suggested tests outside the DCCN use public data or do not use data.
Suggested tests inside the DCCN use private data.