verification: run Map/Reduce and Scheduled probes through the runner

Open
#80 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
typescript
Domain
testing

Research direction

Read docs/verification/automation.md and the related issues #74 and #78 to understand the existing verification flow. The issue calls for starting the script with N/task from the runner and reading the result from a scratch folder, but the scratch location, cleanup, and approval for account writes still need decisions. Done means those decisions are resolved and the Map/Reduce and Scheduled probes run through the runner with results captured.

Written by the indexing model from the issue text.

Description

needs-triage

Part of the follow-up to #74 (see #78 and docs/verification/automation.md).

Start the script with N/task from the runner and read its result from a scratch folder. Needs a decision on the scratch folder, cleanup and approval (it writes to the account).

Dominant language
TypeScript
Stars
1
Forks
0
Avg merge
2h 8m
Merged PRs (30d)
64

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nemchik/biome-plugin-suitescript

All issues in nemchik/biome-plugin-suitescript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.