TrendSpider assessment
Rule development and chart research
A way to investigate a swing rule; a strategy test is not a certified multi-day trading record.
Research task
TrendSpider's strategy-tester documentation describes testing user-defined conditions. A swing buyer should retain the condition, observation timeframe and version alongside the historical test, rather than treating a chart's final annotations as delivered alerts.
Multi-session questions
Specify bar-close timing, entry expiration, holding clock and exit instructions before a forward sample. Record what happens across an earnings announcement or closed market. Backtest settings need to match the stated workflow instead of being changed to rescue a losing example.
Assessment boundary
We have not subscribed to or live-tested this product. Check current plan access and notification behaviour directly. Platform functionality alone does not demonstrate that a rule retains an edge after costs, overnight gaps or missed instructions.
Sources
Keep the rule setting next to the original idea
A rules-based chart workflow should retain the condition version and the action the reader chose when it fired. If a later setting changes, identify whether it governs existing positions or only future candidates. A chart pattern and a held position are different objects: the held position also needs quantity, entry price, carrying debits and a valuation time. Use the ownership and partial-exit guides to document that connection. These questions do not introduce a new measured feature comparison or claim that an unperformed account test occurred.