Feature Import, Navigate and Perform Operations

Overview

After a successful API import, Shift Left Studio organizes your API in this hierarchy:

• Project -> Features -> Endpoints

Features are generated from API resource groups or tags in your OpenAPI specification (for example, Users, Payments, Orders).

In addition to imported features, users can manually manage features using the built-in CRUD actions.

View the project dashboard

After closing the import confirmation screen, you return to the Project Dashboard.

On this screen you can:

• see your newly created project
• review all imported features
• open any feature to inspect its endpoints
• use Add Feature and row-level actions for manual CRUD

Create a feature (manual)

Use this when you want to add a feature that is not yet present or to organize endpoints intentionally.

1. Open the project dashboard.
2. Select Add Feature.
3. In the Add Feature dialog, enter:
   • Name: feature name (for example, Orders)
   • Description: short purpose and scope
4. Select Create Feature.

The new feature appears in the feature table and is ready for endpoint mapping and test work.

Read and browse features

To inspect an existing feature:

1. Locate the feature row in the Features table.
2. Review metadata such as endpoint count, test case count, and coverage.
3. Select the feature name to open endpoint-level details.

Drill down into endpoints

1. Select a feature tile or list row.
2. Review the endpoint list for that feature.
3. Select an endpoint to open the endpoint test case view.

Each endpoint includes method and path information to help you quickly identify where to generate or run tests.

Update a feature (edit)

Use the edit action in the feature row when feature metadata needs correction.

1. In the Features table, locate the feature.
2. Select the Edit action (pencil icon).
3. Update name and/or description.
4. Save changes.

Keep naming consistent with API domain boundaries so reports and navigation remain clear.

Delete a feature

Use the delete action only when the feature is obsolete or created in error.

1. In the Features table, locate the feature.
2. Select the Delete action (trash icon).
3. Confirm deletion in the prompt.

Before deleting, validate impact on linked endpoints and tests to avoid losing expected coverage.

Continue to testing workflow

From endpoint view, continue with:

• test generation
• test editing
• test execution
• result review

See Validate endpoints to confirm endpoint definitions and connectivity. For test design and runs, use Test case and Run tests and review results.

Best practices

• Keep OpenAPI tags consistent so feature grouping stays predictable.
• Use domain-driven feature names for easier navigation.
• Use concise descriptions so team members quickly understand feature scope.
• Re-import and review features whenever the API specification changes.

Related articles

• Project
• Managing projects
• Endpoint management
• Endpoint import and discovery