Welcome to bluepill Discussions!

[ob]

👋 Welcome!

We’re adding Discussions as a place to connect with other people using Bluepill. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we build together 💪.

To get started, comment below with an introduction of yourself and tell us about your ideas.

[ravimandala]

Hi everyone, I am Ravi Mandala from LinkedIn. Bluepill does a great job with test execution, retries and reporting. The swim-lane feature is really useful. We can keep trying to improve the performance and the reporting. A few ideas...

1. Get data from past executions and generate estimated execution times (at test/test_class/target level) by itself.
2. Generate another report just for the time taken by tests in current run, to be used in subsequent runs.
3. More reporting to help flakiness investigation, like trying to answer the question... why did a test pass when retried?
4. Easier way to distinguish newly added tests and a way to run them repeatedly (say 'n' times) to test for flakiness.
5. Some sort of incremental testing with appropriate signals from the client.