Post-Upload Requirements

Overview

After uploading your build to Pie, you’ll need to provide additional information to help Pie’s AI agents test your application effectively. This page outlines what information to send and why it’s important.

How to Submit Information

Send the required information via email to the Pie Labs team. You’ll receive upload confirmation with contact details when you upload your build.

Required Information

1. Authentication Details

Provide test credentials so Pie’s AI agents can access your application.

Test Account Credentials

• Username/Email: Test account login
• Password: Account password
• Additional Factors: 2FA codes, security questions, or PIN codes (if applicable)

Special Login Flows

Document any non-standard authentication requirements:

• Social login (Google, Facebook, Apple) test accounts
• SSO or enterprise login procedures
• Biometric authentication alternatives
• Phone verification bypass codes
• Magic links or email verification

Example:

“Use test account: testuser@example.com / TestPass123. The app will send a verification code to this email. Use code 123456 to bypass email verification in test environment.”

2. Testing Boundaries

Help Pie’s AI understand what to test and what to avoid.

Features to Focus On

List specific features, workflows, or screens that are critical:

• Key user journeys (e.g., “complete a purchase”, “create a new post”)
• Recently updated features that need validation
• Complex workflows requiring thorough testing
• High-priority user flows

Example:

“Focus on: checkout flow, user profile creation, search functionality, and push notification settings.”

Areas to Avoid

Specify features or actions the AI should not test:

• Work-in-progress features
• Known broken functionality
• Admin-only sections
• Features requiring special permissions
• Actions that might trigger alerts or notifications

Example:

“Avoid: admin panel (requires special access), payment processing with real cards, social sharing features (under development).”

Critical User Journeys

Describe end-to-end workflows that must be tested:

Example:

“Critical journey: New user signs up → completes profile → browses products → adds item to cart → proceeds to checkout → completes order. This flow must work seamlessly.”

3. Custom Test Files (If Applicable)

Some applications require specific files for testing.

When to Provide Files

Upload custom files if your app needs:

• Documents: PDFs, Word docs, spreadsheets that users would upload
• Images: Photos, avatars, or other images for testing uploads
• Media: Videos or audio files
• Data Files: CSV, JSON, or XML files for import features
• Test Data: Sample datasets or configuration files

How to Upload Files

• Mention required files in your email to Pie Labs
• Pie team will provide a secure upload link
• Include descriptions of how each file should be used

Example:

“App requires test images for profile photos (JPG, max 5MB) and PDF documents for the document scanner feature. Will upload via provided link.”

Optional Guidelines

While not required, this information helps Pie’s AI test more effectively.

Expected Behavior

Describe how critical features should work:

Example:

“When user adds item to cart, a badge with item count should appear on cart icon. Checkout flow should take 3-4 steps: cart review → shipping info → payment → confirmation.”

Known Issues

List any known bugs or limitations:

Example:

“Known issue: Dark mode toggle sometimes requires app restart. Search results may be slower during peak hours. These are expected and don’t need reporting.”

Specific Test Scenarios

Suggest particular scenarios to test:

Example:

“Test scenarios: 1) User with empty cart tries to checkout 2) User uploads very large image 3) User rapidly switches between tabs 4) User loses network during form submission.”

Performance Benchmarks

Provide performance expectations if relevant:

Example:

“Home screen should load within 2 seconds. Search results should appear within 3 seconds. Video playback should start within 1 second.”

Edge Cases

Highlight unusual situations to test:

Example:

“Edge cases: User with 100+ items in favorites, extremely long usernames (20+ chars), multiple rapid purchases, offline mode usage.”

Information Template

Use this template to structure your submission:

Subject: Test Configuration for [Your App Name]

AUTHENTICATION:
- Username: [test account]
- Password: [password]
- Special Instructions: [any special login steps]

TESTING FOCUS:
- Key Features: [list critical features]
- Avoid: [list areas to skip]
- Critical Journeys: [describe main workflows]

CUSTOM FILES NEEDED:
- [Describe any required test files]

OPTIONAL CONTEXT:
- Expected Behavior: [key behaviors]
- Known Issues: [documented bugs]
- Test Scenarios: [specific scenarios]
- Performance Notes: [benchmarks if applicable]

CONTACT:
- Name: [your name]
- Email: [your email]
- Best time to reach: [timezone/hours]

Best Practices

Security

• ✅ Use dedicated test accounts created specifically for automated testing
• ✅ Ensure test accounts have no access to production data or real user information
• ✅ Use test environment credentials only, never production
• ❌ Never share credentials with access to real user data
• ❌ Never provide production API keys or secrets

Clarity

• ✅ Be specific: “Test the checkout flow” is better than “test payments”
• ✅ Use examples: Show what you mean rather than just describing
• ✅ List steps: Break down complex workflows into numbered steps
• ✅ Highlight priorities: Indicate what’s most important to test

Communication

• ✅ Respond promptly to any follow-up questions from Pie Labs
• ✅ Update information if test accounts or environments change
• ✅ Notify about changes when you upload new builds with different requirements
• ✅ Provide context about your app’s purpose and target users

Account Management

Test Account Setup

Create test accounts that:

• Have appropriate permissions for the features you want tested
• Won’t trigger rate limits or security alerts
• Represent different user roles if your app has role-based access
• Have realistic test data (profile info, settings, history)

Multiple User Roles

If your app has different user types, provide accounts for each:

Example:

“Two test accounts provided:

1. Regular user: user@test.com / UserPass123
2. Premium user: premium@test.com / PremPass123 Premium account has access to advanced features and ad-free experience.”

Account Lifecycle

Inform Pie Labs about:

• Account expiration dates (if any)
• Password rotation schedules
• When test environment resets occur
• Maintenance windows that affect test accounts

Environment Details

Test Environment Information

Provide context about your test environment:

Example:

“Test environment: https://staging.example.com

• Database resets nightly at 2 AM UTC
• Payment processing uses Stripe test mode
• Email notifications disabled
• Push notifications functional”

Data Persistence

Clarify what happens to test data:

Example:

“Test data persists for 7 days, then automatically purges. Feel free to create, modify, or delete any data. Environment resets every Sunday at midnight UTC.”

What Happens Next?

After submitting this information:

1. Confirmation: Pie Labs team confirms receipt (usually within 24 hours)
2. Setup: Team configures testing parameters based on your requirements
3. Testing Begins: AI agents start testing within 30 minutes of setup
4. Issue Reports: You’ll receive reports of any issues discovered
5. Ongoing Communication: Team may reach out with questions or updates

Need to Update Information?

If anything changes after your initial submission:

• Email the Pie Labs team with updates
• Use the same subject line as your original email (for threading)
• Clearly indicate what has changed
• Provide new credentials if test accounts change

Example Submission

Here’s a complete example:

Subject: Test Configuration for ShopEasy Mobile App

AUTHENTICATION:
- Username: test.user@shopeasy.com
- Password: TestShop2024!
- Note: App will show a verification code on login screen in test mode. 
  Any 6-digit code works for test accounts.

TESTING FOCUS:
- Key Features: Product browsing, search, cart management, checkout flow, 
  order history, wishlist, user profile editing
- Avoid: Admin dashboard (requires special access), refer-a-friend feature 
  (not yet functional), seller portal
- Critical Journey: Browse products → Add 3 items to cart → Apply promo code 
  "TEST10" for 10% off → Complete checkout → View order confirmation

CUSTOM FILES NEEDED:
- No custom files required. All product images and data pre-loaded in test environment.

OPTIONAL CONTEXT:
- Expected Behavior: Cart icon badge shows item count. Checkout requires 
  shipping address before payment. Order confirmation includes order number.
- Known Issues: Dark mode theme slightly inconsistent on product detail pages. 
  This is expected and already tracked.
- Test Scenarios: Try searching for "shoes", filtering by price, sorting results, 
  adding items to wishlist, updating cart quantities
- Performance: Home screen loads in under 2s, search results in under 1s

CONTACT:
- Name: Jane Doe
- Email: jane.doe@shopeasy.com
- Best time to reach: 9 AM - 5 PM EST, Monday-Friday

Questions?

If you’re unsure what information to provide or need clarification:

• Email the Pie Labs team with your questions
• Reference this guide and mention which section you need help with
• Provide context about your app and specific concerns

The team is here to help you get set up successfully!