thinkScript strategy workflow
Backtesting on thinkorswim means applying a thinkScript strategy to historical chart bars and reviewing its simulated orders and report under stated assumptions.
Source review completed
Prompt brief
ThinkScript · one source file
Example request
Create a long-only thinkScript strategy that enters on a confirmed 20/50 EMA crossover, exits on the reverse crossover, exposes trade size as an input, and avoids repeated entries while already long.
In thinkorswim desktop, add a thinkScript strategy to a chart, choose the symbol, aggregation, loaded history, and trade size, then right-click a strategy arrow and choose Show Report. Inspect the AddOrder price and timing rules. Record commission and slippage assumptions separately; do not assume the native report has deducted them.
Practical workflow
Define entries, exits, repeated-signal handling, position direction, and any session filter so another person could reproduce the same decisions from the same bars.
Represent the rules in one strategy source file. Add explicit inputs and use AddOrder only for the simulated entries and exits you intend to measure.
Set the symbol, aggregation, loaded history, session, default trade size, and repeated-entry settings. Inspect any size or fill-price override in the source. Keep a separate cost worksheet unless the calculation explicitly models costs.
Right-click a strategy arrow and select Show Report. Inspect timestamps, quantities, prices, and P/L for individual orders. Derive additional risk measures separately and repeat the analysis on unseen dates and less favorable costs.
Historical simulated performance is sensitive to data and assumptions. It does not demonstrate future profitability or executable live fills.
A thinkorswim strategy annotates historical bars with simulated orders. The strategy report summarizes the trades produced by that source on the current chart context. Changing the aggregation, date range, or strategy properties can change the trade sequence and reported outcome.
Preserve the code, inputs, chart settings, and a separate record of cost adjustments. The documented Global Settings controls do not establish that commission or slippage has been deducted from report P/L.
Pineify can turn explicit rules into an editable strategy and revise the source. It does not run the native thinkorswim report or validate the broker data used by the platform.
Review bar offsets for future data, confirm the intended price is used for each condition, and test whether the first usable bar has enough history. Then compare a sample of simulated orders with the underlying bars.
AddOrder schedules a simulated order for the next bar; its default price is open[-1], the next bar open. That default execution-price reference is different from using future prices to decide whether to enter. Do not assume a signal at the current close fills at that close.
For a hypothetical 100-share trade, buying at 50 and selling at 51 gives $100 gross P/L. Assuming $0.02 adverse slippage per share on each side and $1 commission per order leaves $94: 100 - 4 - 2. This is arithmetic under stated assumptions, not a thinkorswim result or evidence of achievable fills.
Pineify thinkScript workflow
Give the Coding Agent the formula, inputs, plots, alerts, and edge cases. It returns one editable study or strategy file and keeps focused revisions in the same code artifact.
A thinkorswim script is source code written in thinkScript. Most chart scripts are studies that calculate plots, labels, colors, or alerts, or strategies that add simulated orders for historical analysis. Pineify can generate and revise one editable study or strategy file from a plain-English specification.
Read guideIn thinkorswim desktop, open Charts, select Studies, then Edit Studies. Choose Create for a study, or open the Strategies tab and create a strategy. Paste the thinkScript source into the editor, give it a unique name, save it, and add it to the chart. For a saved thinkScript .ts file, use Import in Tools > thinkScript IDE and select Study or Strategy. Fix every parser error before treating the script as installed.
Read guidethinkorswim includes a studies library for common indicators and a thinkScript editor for custom studies. There is no universal best indicator for day trading. Select a study by its calculation, inputs, chart context, and failure modes, then test whether its signal adds information beyond price alone.
Read guideLast verified:
Pineify provides information and code-generation assistance, not investment advice. Generated scripts, strategy reports, simulations, and historical examples cannot predict prices or guarantee returns. Review every script and test it in its target platform before relying on its output.
Yes. Add a thinkScript strategy to a chart and review its simulated orders and strategy report. The result depends on the source, chart data, inputs, and strategy properties.
A study calculates chart output such as plots or alerts. A strategy adds simulated orders so specified rules can be reviewed on historical chart data.
No. Pineify generates or edits the thinkScript strategy source. You run the strategy and inspect its report inside thinkorswim.
Generate one editable thinkScript study or strategy, inspect the source, request focused changes, and complete the final check in thinkorswim.
Pineify generates source code. Review its syntax and chart behavior in thinkorswim before use.
