1 / 28

QA/Testing @Synerzip

QA/Testing @Synerzip. October 2008. Discussion Topics. Synerzip Overview QA/Testing Capabilities Overview Best Practices. About Us (Synerzip in a Nut-shell). Software development partner for small/mid-sized technology companies Focus: B/C round funded technology companies

iolaj
Download Presentation

QA/Testing @Synerzip

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. QA/Testing @Synerzip October 2008 www.synerzip.com

  2. Discussion Topics • Synerzip Overview • QA/Testing Capabilities • Overview • Best Practices Confidential

  3. About Us (Synerzip in a Nut-shell) • Software development partner for small/mid-sized technology companies • Focus: B/C round funded technology companies • Deep experience in product development, testing, & deployment • Handles full software development life cycle • Technology and industry domain agnostic • Engagement flexibility: Fixed-Price OR Dedicated-Team • Actually reduces risk of development/delivery • Experienced software management team • Brings in appropriate level of engineering discipline • Follows Agile development process – responsive & disciplined • Reduces cost – dual-shore team providing 50% cost advantage • Offers long term flexibility – allows (facilitates) taking offshore team captive Confidential

  4. Experienced Team Team of seasoned professionals with extensive experience in offshore software Product Development • Hemant Elhence, Chief Executive Officer • Co-founder & COO of ECMi (Dallas), venture funded software product company • Product-line VP at i2 – managed product portfolio with multiple offshore teams • Manager at McKinsey & Co (Dallas), Consultant at TRG (Boston) • Software engineer at Digital Equipment Corporation (Boston) • BSEE IIT Delhi, MSEE Univ. of Massachusetts, MBA Univ. of Chicago • Vinayak Joglekar, EVP & Chief Technology Officer • Co-founder & CTO of ECMi, lead offshore (India) development center • 22+ years experience in software architecture design & product development, has built and mentored 100+ teams, hired 1000+ software professionals • Successfully delivered off-shore software projects for 20+ companies incl. Alfa-Laval, First Guarantty, Cyberdrawer, etc. • BSME IIT Bombay, MBA IIM Calcutta Confidential

  5. Our Clients Confidential

  6. QA/Testing Maintenance • Automation • Performance/usability • Stress/compatibility Product Development Application Integration Related Services Customer Support • Data Entry • BPO Configuration/ Deployment Data Prep & Loading • Full solution provider for small/mid-sized technology company • – Able to handle all related services • – Puts together tailored team and processes Services Scope Confidential

  7. Technology Skills Synerzip team offers skills for variety of front end, back and helper tools in open source as well as the licensed software. Confidential

  8. Discussion Topics • Synerzip Overview • QA/Testing Capabilities • Overview • Best Practices Confidential

  9. Why Leverage Synerzip for QA • Third-party authentication - independent, “outside-in” perspective • Leverage Synerzip’s cumulative experience - repository of know-how and best practices • Leverage specialized skills and processes • Technical e.g. Automation, Load/Performance Testing, Usability testing • Test Strategy Design • Test Management e.g. estimation, project management, metrics • Access to flexible capacity – ability to increase/decrease capacity on-demand • Gain cost advantage of dual-shore operation Confidential

  10. Handles Full Scope of Testing Testing Triad Confidential

  11. Testing Activities with SDLC Confidential

  12. Importance of Testing in SDLC • Testing requires 40% of total efforts in SDLC • Release decisions can be based on hard testing data, thus with proper risk assessment • Fixing of defects earlier in the SDLC is much cheaper! • Agile methodology – Test driven development Confidential

  13. Discussion Topics • Synerzip Overview • QA/Testing Capabilities • Overview • Best Practices Confidential

  14. QA Best Practices QA Process Test case management Bug Tracking Test automation Performance Testing Confidential Confidential

  15. QA Process We recommend and follow Agile methodologies as a part of QA Process Agile methodologies generally promote: A project management process that encourages frequent inspection and adaptation. Each iteration is worked on by a team through a full software development cycle, including planning, requirements analysis, design, coding, unit testing, and progress. As a part of Agile process we use following tools and techniques such as continuous integration,Fitnesse,nUnit/XUnit etc. Confidential Confidential

  16. Test Strategy Test planning Use cases Test case documentation Test case execution ( Black box , white box testing) System Testing Acceptance Testing Usability Testing Compatibility Testing Continue Test case update Test automation (Automate regression test suite) Confidential Confidential

  17. Test Strategy (Continued) Understanding of requirements 1 Start preparing flow chart / block diagram based on the understanding and verify. 2 Come up with use case diagrams. 3 Prepare Test out line document and get it reviewed. 4 Prepare Detail testcase document 5 Execute it during each test cycle. 6 Ad-Hoc Testing 7 Automate regression Test suite. 8 Prepare Customer scenarios document support team. 9 User acceptance /Performance /Security Testing 10 Confidential Confidential

  18. System Testing Volume and stress testing: Can the system handle the required data throughput, requests etc? What are the upper bounds? Configuration testing: Does the system operate correctly on all the required software and hardware configuration? Resource management testing: Can the system exceed memory allocation limits? Security testing: Is the system secure enough? Recovery testing: Use pathological test cases to test system recovery capabilities. Availability/reliability: Does the system meet the requirements? Confidential Confidential

  19. Test case management We use opensource free tool TestLink (http://testlink.org/wordpress/) for doing test case management. TestLink is a web based tool TestLink enables easily to create and manage Test cases as well as organize them into Test plans. Test plans allow team members to execute Test cases and track test results dynamically, generate reports, trace software requirements, prioritize and assign tasks. The tool has web based and its really useful for management to track the testing status as per build. It cooperates with known Bug tracking systems as is Bugzilla, Mantis and few more. Confidential Confidential

  20. Test Metrics We maintain the metrics generated by the Testlink itself General Test Plan Metrics Overall Build Status Query Metrics ( user can form a query for e.g. build , top level test suite start time , end time etc.) Failed Test Cases Blocked Test Cases Not run Test Cases Total bugs for each testcase. Charts ( Pie charts etc.) Confidential Confidential

  21. Bug Tracking We are familiar with BugZilla, Mantis, Test track pro, etc. We make sure that all the required details are there in the defect including good summary, environment description, Proper steps , attachments /screenshots etc. Confidential Confidential

  22. Test automation We believe in test automation and we generally try to achieve 80-90% of the testing using automated test suites. Based on the application we evaluate different tools. We run the complete automated suite after every build release. We use tools such as Selenium, Watir , Ruby , Perl, TCL. Confidential Confidential

  23. Performance Testing We conduct performance testing to determine how fast some aspect of system performs under particular work load We recommend load as well as stress testing. We recommend opensource tool WebLoad (http://www.webload.org/) , OpenSTA http://opensta.org/ Confidential Confidential

  24. Load Testing A load test is usually conducted to understand the behavior of the application under a specific expected load. Parameters used will be: Response Time Throughput Resource Utilization Tools like Jmeter, OpenSTA, LoadRunner, Selenium can be used Confidential Confidential

  25. Stress Testing This testing is normally used to determine the outer limits of the application. Tests are re-run with incremental number of users until the application breaks down. Tools like Jmeter, OpenSTA, LoadRunner, Selenium can be used Confidential Confidential

  26. Typical Performance Metrics Confidential Confidential

  27. Questions? Confidential Confidential

  28. Contact Information • Hemant Elhence (Dallas based) • hemant@synerzip.com • Cell Phone: 214.762.4873 • www.synerzip.com • HQ in Dallas, TX • 14228 Midway Rd, #130, Dallas, TX 75244 • Office Tel: 469.322.0349 • Office Fax: 469.322.0490 Confidential

More Related