โ† All MTA Flashcard Decks

Software Testing Fundamentals Flashcards

7 cards from real MTA practice questions. Tap to flip, then mark Knew It or Still Learning โ€” missed cards come back until you master them.

Read the first 7 Software Testing Fundamentals flashcards as text
  1. What is alpha testing?

    Answer: Testing conducted internally by the development or QA team before external release

    Alpha testing is conducted by the internal team to identify bugs before the software is released to external beta testers or users.

  2. What is beta testing?

    Answer: Testing performed by real end users in a near-production environment before official release

    Beta testing is conducted by actual end users or customers in a real-world environment to find bugs before the final product launch.

  3. What is equivalence partitioning in software testing?

    Answer: Dividing input data into classes where all values in a class are expected to behave the same

    Equivalence partitioning groups inputs into valid and invalid partitions so that testing one value from each partition covers all similar inputs.

  4. What does boundary value analysis focus on?

    Answer: Testing values at and just beyond the edges of valid input ranges

    Boundary value analysis targets values at the exact boundaries of input ranges, where software defects are most likely to occur.

  5. What is smoke testing?

    Answer: A quick preliminary test to verify that critical basic functions work before deeper testing begins

    Smoke testing (also called build verification testing) checks that the most critical functions work so that more detailed testing is worthwhile.

  6. Which type of testing evaluates how a system behaves under expected and peak load conditions?

    Answer: Performance testing

    Performance testing measures system responsiveness, stability, and scalability under various load levels to ensure acceptable behavior.

  7. What is User Acceptance Testing (UAT)?

    Answer: Testing conducted by intended end users to confirm the system meets their business requirements

    UAT is the final validation phase where end users verify the system meets their actual business requirements before it goes live.