wp-cli/export-command
2
0
Fork 0
mirror of https://hk.gh-proxy.com/https://github.com/wp-cli/profile-command.git synced 2025-08-20 06:30:56 +08:00
Code Issues Projects Packages Activity Actions
export-command/features/profile-stage.feature

163 lines
5.3 KiB
Gherkin
Raw Normal View History

Register some basic hooks for the template stage
2016-08-30 06:57:55 -07:00
Feature: Profile the template render stage
Split `wp profile` into `wp profile stage` and `wp profile hook`
2016-10-04 06:47:01 -07:00
Scenario: Profiler loads a summary table
Given a WP install
When I run `wp profile stage --fields=stage`
Then STDOUT should be a table containing rows:
| stage |
| bootstrap |
| main_query |
| template |
Register some basic hooks for the template stage
2016-08-30 06:57:55 -07:00
Scenario: Profiler loads a table with the correct hooks
Given a WP install
Assert hooks for each stage
2016-10-07 15:58:08 -07:00
When I run `wp profile stage bootstrap --fields=hook`
Then STDOUT should be a table containing rows:
Put names to the intermediate stages For the most part, it's `<hook>:before`, except when it's the last hook in the sequence.
2016-10-09 09:05:27 -07:00
| hook |
| muplugins_loaded:before |
| muplugins_loaded |
| plugins_loaded:before |
| plugins_loaded |
| setup_theme:before |
| setup_theme |
| after_setup_theme:before |
| after_setup_theme |
| init:before |
| init |
| wp_loaded:before |
| wp_loaded |
| wp_loaded:after |
Use an explicit flag to indicate when the total should be displayed
2016-10-26 06:38:17 -07:00
| total (13) |
Assert hooks for each stage
2016-10-07 15:58:08 -07:00
When I run `wp profile stage main_query --fields=hook`
Then STDOUT should be a table containing rows:
Put names to the intermediate stages For the most part, it's `<hook>:before`, except when it's the last hook in the sequence.
2016-10-09 09:05:27 -07:00
| hook |
| parse_request:before |
| parse_request |
| send_headers:before |
| send_headers |
| pre_get_posts:before |
| pre_get_posts |
| the_posts:before |
| the_posts |
| wp:before |
| wp |
| wp:after |
Use an explicit flag to indicate when the total should be displayed
2016-10-26 06:38:17 -07:00
| total (11) |
Assert hooks for each stage
2016-10-07 15:58:08 -07:00
Split `wp profile` into `wp profile stage` and `wp profile hook`
2016-10-04 06:47:01 -07:00
When I run `wp profile stage template --fields=hook`
Register some basic hooks for the template stage
2016-08-30 06:57:55 -07:00
Then STDOUT should be a table containing rows:
Put names to the intermediate stages For the most part, it's `<hook>:before`, except when it's the last hook in the sequence.
2016-10-09 09:05:27 -07:00
| hook |
| template_redirect:before |
| template_redirect |
| template_include:before |
| template_include |
| wp_head:before |
| wp_head |
| loop_start:before |
| loop_start |
| loop_end:before |
| loop_end |
| wp_footer:before |
| wp_footer |
| wp_footer:after |
Use an explicit flag to indicate when the total should be displayed
2016-10-26 06:38:17 -07:00
| total (13) |
Use --all flag to profile all stages
2016-10-07 15:45:48 -07:00
GH#36 Added functional test
2017-10-11 15:44:08 +05:30
When I run `wp profile stage template --fields=hook --orderby=hook --order=DESC`
Then STDOUT should be a table containing rows:
| hook |
| wp_head:before |
| wp_head |
| wp_footer:before |
| wp_footer:after |
| wp_footer |
| template_redirect:before |
| template_redirect |
| template_include:before |
| template_include |
| loop_start:before |
| loop_start |
| loop_end:before |
| loop_end |
| total (13) |
Use --all flag to profile all stages
2016-10-07 15:45:48 -07:00
Scenario: Use --all flag to profile all stages
Given a WP install
When I run `wp profile stage --all --fields=hook`
Then STDOUT should be a table containing rows:
Put names to the intermediate stages For the most part, it's `<hook>:before`, except when it's the last hook in the sequence.
2016-10-09 09:05:27 -07:00
| hook |
| muplugins_loaded:before |
| muplugins_loaded |
| plugins_loaded:before |
| plugins_loaded |
| setup_theme:before |
| setup_theme |
| after_setup_theme:before |
| after_setup_theme |
| init:before |
| init |
| wp_loaded:before |
| wp_loaded |
| parse_request:before |
| parse_request |
| send_headers:before |
| send_headers |
| pre_get_posts:before |
| pre_get_posts |
| the_posts:before |
| the_posts |
| wp:before |
| wp |
| template_redirect:before |
| template_redirect |
| template_include:before |
| template_include |
| wp_head:before |
| wp_head |
| loop_start:before |
| loop_start |
| loop_end:before |
| loop_end |
| wp_footer:before |
| wp_footer |
| wp_footer:after |
Use an explicit flag to indicate when the total should be displayed
2016-10-26 06:38:17 -07:00
| total (35) |
Use --all flag to profile all stages
2016-10-07 15:45:48 -07:00
Scenario: Invalid stage specified
Given a WP install
When I try `wp profile stage foo_bar`
Then STDERR should be:
"""
Error: Invalid stage. Must be one of bootstrap, main_query, template, or use --all.
"""
Indicate callback count when profiling a stage
2016-10-07 16:18:04 -07:00
Scenario: Identify callback_count for each hook
Given a WP install
When I run `wp profile stage bootstrap --fields=hook,callback_count`
Then STDOUT should be a table containing rows:
| hook | callback_count |
| plugins_loaded | 3 |
Use `--spotlight` to filter zero-ish results from the set
2016-10-26 05:40:34 -07:00
Scenario: Use spotlight mode to filter out the zero-ish values
Given a WP install
When I run `wp profile stage bootstrap --fields=hook`
Then STDOUT should be a table containing rows:
| hook |
| init |
| wp_loaded:before |
| wp_loaded |
| wp_loaded:after |
When I run `wp profile stage bootstrap --fields=hook --spotlight`
Then STDOUT should be a table containing rows:
| hook |
| init |
| wp_loaded:after |
Reference in a new issue Copy permalink