Aptos Indexer Testing Framework Overview

The Aptos Indexer Testing Framework provides two methods to generate testing transactions: Importer and Move Scripts. Both approaches are suited for specific scenarios based on your development and testing requirements, enabling you to test how your system handles various transaction types.

When to Use Importer

1. Fetching Historical Transactions

• Retrieve specific historical transactions from the Aptos blockchain (Testnet or Mainnet) for testing or analysis.
• Ideal for creating mocked transaction inputs for processor tests or regression checks.

2. Simulating Real-World Scenarios

• Validate processor logic or database integrity by replaying transactions from live networks.
• Simulate conditions that mirror real-world environments to ensure robustness.

When to Use Move Script

1. Deploying Custom Logic

• Write, deploy, and execute custom logic using Move to test your new AIPs (Aptos Improvement Proposals).
• Ideal for creating smart contracts, defining new modules, or implementing specific on-chain functionalities.

2. Prototyping New Features

• Experiment with new decentralized application (dApp) ideas or test custom on-chain workflows.
• Perform operations like:
  • Account creation
  • Token minting
  • Custom transactions
• Define business rules and execute state changes directly on the Aptos blockchain.

Summary

Both Importer and Move Scripts are essential tools in the Aptos Indexer Testing Framework. Use the Importer for replaying and analyzing real-world transactions, while Move Scripts are best for testing custom logic and prototyping features. Choose the method that aligns with your testing goals to ensure a comprehensive validation process.