M1 - Fiki and Project Description

Automate your UI QA testing by using ATF to find and write scripts.

View the project on GitHub View Landing page View Fiki page Members




Alistar

Andreea Alistar

Front-End Engineer

andreealistar@gmail.com

Contact

Andrei

Andrei Crividenco

Full Stack + QA Engineer

acrividenco@gmail.com

Contact

Cirimpei

Cirimpei Dumitru

Backend Architect + QA

cirimpei.dumitru@gmail.com

Contact

Cirimpei

Eugen Draguteanu

Front-End Engineer

eugen.draguteanu@gmail.com

Contact

1. Why ATF should be your favorite product testing tool?


A. No More Writing Scripts: No complicated training required. No complex test builders. No “live” test building. Real automation.

B. Avoid Costly Mistakes: Manual QA is prone to errors that can cost millions. Diligently test your systems and find more bugs.

C. Simplify Testing: Verify tests at a glance. ATF makes it easy to identify the path of each test.

D. Find Bugs Faster: Run your tests simultaneously so you can get more done in less time.

E. Easily Maintain Tests: Run and verify your tests. Teach ATF about your system and it will update tests for you.

F. Ensure Cross-Browser Consistency: Support for testing in Chrome and Firefox. Compare browser screenshots.

2. ATF's Agile Team


What we want to achieve?

Test automation is living, breathing code and is developed to provide sanity checks for ever-changing production code. Building an automated testing framework can make your testing scalable, reliable, efficient, cost-effective and less brittle.

What we need?

The team needed an experienced understanding of software testing and QA to know how to achieve the right balance of manual, UI, integration (API) and unit tests.




3. Describe the problem that you have noticed


You would review PRODUCTION code, wouldn’t you? You should review test code, too.



  • Cost of Software Failures Annually: $1.1 Trillion lost && 315.5 Lost years;

  • The current frameworks have limited features;

  • Expensive for what if offers (license or subscription costs of commercial automation solutions);

    • We created a framework that allows a single engineer to do the work of a QA team. Find more bugs. Save times and money.


    We are going to present some desavantages of top 3 QA tools used by most of the people in this industry:


  • BrowserStack
  • Apache Jmeter
  • Sauce Labs

    • BrowserStack versus ATF


  • Doesn't have the ability to write tests and save them in the platform. It gives you the opportunity to run tests locally (you have them stored locally & run on their infrastructure, but the test code itself it's on your computer).

  • BrowserStack tends to be rather expensive and the free option is very limited. I'd like to see a unlimited free option if even for one person.

  • No faster response times on bringing in the site screenshots.

  • Doesn't have the ability to test multiple browsers at the same time.

  • Can run only one site at a time. It's not very flexible to switch from one page/site to another. Have to restart the view each time.

    • Solution? ATF

    ATF meets BrowserStack’s drawbacks!



    Apache Jmeter versus ATF


  • Reporting and graph visualization aren't that great. The option of adding external plugins for reporting does enhance it to some extent but not anywhere what we can get from Industry standard tools.

  • Overall look to the modern like interface should be improved.

  • More real world examples to help with learning the product.

  • Recording of tests is very complex for a user with less programming skills.

  • Documentation is not user-friendly, you may need quite an extensive amount of time to resolve an issue.

    • Solution? ATF

    ATF meets Apache Jmeter’s drawbacks!



    Sauce Labs versus ATF


  • Usually, the platform becomes unresponsive and tests fail without any significant reason.

  • The tests should be a little faster since the time for the tests to complete is a bit slow.

  • Cloud service is a bit sluggish. When run it, it takes a substantially long period of time to finish executions. It is bit sluggish and took at some point to carry out action.

  • No integrated CI system. Doesn't provide a mechanism to run tests on a schedule or integrate with GitHub.


    • Solution? ATF

    ATF meets Sauce Labs’ drawbacks!



    4. Your solutions proposed / value proposition


    A. Easy management of the test cases;

    B. Speed to deployment: get the product to market 30% faster;

    C. Cost-effective: 60% reduction in total QA costs;

    D. Productivity: Up to 90% less development time for QA engineer;

    E. Intuitive GUI that immediately shows when, where and how the execution failed;

    5. Customer segment/s


    A. Corporate IT with complex software solutions;

    B. Small and medium businesses with a web app or a complex website;

    C. Freelancers / students working on software projects;

    The main focus is going to be on B. Small and medium businesses. We are thinking to reach ING Tech, which has distributed teams that doesn't have a QA process already set up.


    6. Competition





    centered image




    centered image

    7. Your advantage over the competition


    A. Competitive price:

    • $200 Per Test Search and $0.10 Per Test Run. Our smallest plan starts at $500/month and includes 2 discoveries and 1000 test (plans average at ~$3.500/month). Actual products have expensive license or subscription costs;
    B. Ease management of the test cases:

    • Building and running automated tests/test suites & View test results
    • Identify and resolve client errors
    • Compare results and execution times for different automated test and suite results & Re-run failed tests in an automated test suite
    • Cancelling automated tests and test suites & Copy automated test
    C. No advertising, no clutter;

    D. Fast support (24/7) available for our customers;

    E. Offer plugins for special features (the product will stick to the most necessary features - actual products have GUI ambiguous due to the need of providing access to every feature);

    F. Intuitive GUI that immediately shows WHEN, WHERE and HOW the execution failed;

    8. Key metrics


    A. Customer satisfaction;

    B. Failure rates;

    C. Server uptime;

    D. Adoption rate;

    E. Runtime test overhead;

    9. Cost structure


    A. Marketplace for special plugins and features: storing tests in the CLOUD, SCM for the tests, custom user intefaces;

    B. Cloud storage;

    C. Technology costs: $2k / month;

    D. Marketing costs (Google AdSense (for promoting)): $3k / month;

    E. Legal costs: $15k

    F. Employees;

    Competitive costs & a donation button will be available on the main download page (revenue is equally divided);

    10. Revenue streams


    A. Donations;

    • 1$ - Ten hours of electricity for one developer PC!
    • 5$ - One day webserver hosting!

    B. Paid modules: Connect to DB, Connect to RabbitMQ, etc. We are going to sell the modules that we implemented for our product.;

    C. Feature for running tests in parallel;

    D. Feature for running tests in a specific environment (browser/OS);

    E. Cloud storage space for the tests;

    F. SCM feature for the tests;

    G. $200 Per Test Search and $0.10 Per Test Run. Our smallest plan starts at $500/month and includes 2 discoveries and 1000 test (plans average at ~$3.500/month) - Check the price on our landing page