1"use strict";(self.webpackChunkshaft_user_guide=self.webpackChunkshaft_user_guide||[]).push([["34220"],{1753(e){e.exports=JSON.parse('{"tag":{"label":"installation","permalink":"/docs/tags/installation","allTagsPath":"/docs/tags","count":7,"items":[{"id":"journeys/create-a-project","title":"Create a project and run the sample","description":"Generate a Maven project, run its sample test, and open the report.","permalink":"/docs/journeys/create-a-project"},{"id":"start/local-infrastructure/mobile","title":"Install managed mobile infrastructure","description":"Plan, approve, and install SHAFT-owned Android SDK, emulator, and Appium, or iOS and Windows Appium drivers.","permalink":"/docs/start/local-infrastructure/mobile"},{"id":"start/local-infrastructure/services","title":"Install managed services and tools","description":"Plan, approve, and install SHAFT-owned Selenium Grid, Healenium, ReportPortal, BrowserStack Local, Playwright browsers, and Lighthouse, and diagnose agent tools.","permalink":"/docs/start/local-infrastructure/services"},{"id":"start/installation","title":"Install SHAFT","description":"Generate a new SHAFT project or upgrade an existing automation project.","permalink":"/docs/start/installation"},{"id":"start/local-infrastructure/reference","title":"Local infrastructure reference","description":"Plan and install policy options, the SHAFT.Infrastructure Java API and properties, and shaft-cli setup exit codes.","permalink":"/docs/start/local-infrastructure/reference"},{"id":"start/local-infrastructure/previews","title":"Preview managed local AI and OCR setup","description":"Evaluate the managed LOCAL_AI provider and the unreleased managed OCR setup from a source build.","permalink":"/docs/start/local-infrastructure/previews"},{"id":"start/local-infrastructure","title":"Set up local infrastructure","description":"Diagnose, plan, approve, and install SHAFT-
1owned local tools through shaft-cli or Java.","permalink":"/docs/start/local-infrastructure"}],"unlisted":false}}')}}]);
Line numbers count LF bytes from the start of the resource, as the search results do. Vendor segments are library code the classifier recognised; they are stored but not indexed. Bytes are shown as Latin1 characters, one per byte.