Page Comparison

...

• Principles / Strategy

  • Are there any testing principles you have formed over time that may be transferable to us?

  • Are there any best practices you generally recommend regarding the test pyramid?

    • What type of functionality should be tested by each type of test: Unit, Integration, Acceptance, Smoke, Component, Contract-based, etc?

    • Unit Tests

      • What are some guard rails that would be useful for Unit tests?

      • What do you mean by “transitive dependency” when assessing a Unit test?

      • Do you have any recommendations on how we may move away from our current state of tightly-coupled tests in the monolith to something more sustainable to maintain?

    • Acceptance Tests

      • We have many Selenium-based (Bokchoy) tests in our monolith that test unhappy paths. Do you have any recommendations for us?

  • Contract based testing seems to be the new hotness, what are your thoughts on using contract based testing as a replacement for selenium/cypress style tests?

    • This is in our legacy systems where the backend provides the rendered html/js to the end user.

• API Testing

  • Any past learnings from testing REST APIs?

  • Any new developments in this space that you’re considering?

• Production Testing

  • Can you share your experiences thus far with New Relic Synthetic-based Testing? When is this tool useful?

• Test Data

  • Any recommendations on how to design and maintain test data used in tests?

• Processes

  • Any processes that you’ve found to be useful for sustaining quality in your organization?

  • Any pro-tips on facilitating and learning from RCAs?

  • Can you share your past experiences with annotating tests?

...