Skip to content
This repository was archived by the owner on May 17, 2019. It is now read-only.

Fix links to the article "Writing Plugin Test Code" #578

Merged
merged 1 commit into from
Oct 24, 2018
Merged

Fix links to the article "Writing Plugin Test Code" #578

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/v1.0/api-plugin-filter.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -142,6 +142,6 @@ Lifecycle of plugins and test drivers is:
4. Run test code (provided as a block for ``d.run``)
5. Assert results of tests by data provided from driver

Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](api-plugin-test) for details.
Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](plugin-test-code) for details.

For configuration tests, repeat 1-2. For full feature tests, repeat 1-5. Test drivers and helper methods will support it.
2 changes: 1 addition & 1 deletion docs/v1.0/api-plugin-formatter.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,7 @@ Lifecycle of plugins and test drivers is:
3. Run test code
4. Assert results of tests by data provided from driver

Test drivers instantiate the plugin. See LINK:[Testing API for plugins](api-plugin-test) for details.
Test drivers instantiate the plugin. See LINK:[Testing API for plugins](plugin-test-code) for details.

For configuration tests, repeat 1-2. For full feature tests, repeat 1-4. Test drivers and helper methods will support it.

2 changes: 1 addition & 1 deletion docs/v1.0/api-plugin-input.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -161,6 +161,6 @@ Lifecycle of plugins and test drivers is:
4. Run test code (provided as a block for ``d.run``)
5. Assert results of tests by data provided from driver

Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](api-plugin-test) for details.
Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](plugin-test-code) for details.

For configuration tests, repeat 1-2. For full feature tests, repeat 1-5. Test drivers and helper methods will support it.
2 changes: 1 addition & 1 deletion docs/v1.0/api-plugin-output.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -459,7 +459,7 @@ Lifecycle of plugins and test drivers is:
4. Run test code (provided as a block for ``d.run``)
5. Assert results of tests by data provided from driver

Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](api-plugin-test) for details.
Test drivers calls methods for plugin lifecycles at the beginning of 4. (``#start``) and the end of 4. (``#stop``, ``#shutdown``, ...). It can be skipped by optional arguments of ``#run``. See LINK:[Testing API for plugins](plugin-test-code) for details.

For configuration tests, repeat 1-2. For full feature tests, repeat 1-5. Test drivers and helper methods will support it.

Expand Down
2 changes: 1 addition & 1 deletion docs/v1.0/api-plugin-parser.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,7 +167,7 @@ Lifecycle of plugins and test drivers is:
3. Run test code
4. Assert results of tests by data provided from driver

Test drivers instantiate the plugin. See LINK:[Testing API for plugins](api-plugin-test) for details.
Test drivers instantiate the plugin. See LINK:[Testing API for plugins](plugin-test-code) for details.

For configuration tests, repeat 1-2. For full feature tests, repeat 1-4. Test drivers and helper methods will support it.

1 change: 0 additions & 1 deletion lib/toc.en.v0.14.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -356,7 +356,6 @@
article 'api-plugin-buffer', 'Writing Buffer Plugins'
article 'api-plugin-base', 'Plugin Base Class API'
article 'api-config-types', 'Types of Configuration Parameters'
# article 'api-plugin-test', 'Testing API for plugins'
end
category 'plugin-helpers', 'Plugin Helper APIs' do
article 'api-plugin-helper-child_process', 'ChildProcess Plugin Helper API'
Expand Down
1 change: 0 additions & 1 deletion lib/toc.en.v1.0.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -362,7 +362,6 @@
article 'api-plugin-buffer', 'Writing Buffer Plugins'
article 'api-plugin-base', 'Plugin Base Class API'
article 'api-config-types', 'Types of Configuration Parameters'
# article 'api-plugin-test', 'Testing API for plugins'
end
category 'plugin-helpers', 'Plugin Helper APIs' do
article 'api-plugin-helper-child_process', 'ChildProcess Plugin Helper API'
Expand Down