Software Design Engineer In Test (sdet) Resume
2.00/5 (Submit Your Rating)
SUMMARY:
- A passion for emerging markets, technologies and entertainment/media experiences in online services that deliver "Anywhere you go THERE YOU ARE" value to customers
- Experience in test automation and Confidential dev tools adding efficiency & coverage:
- C# class library development to support UI automation
- C#/.NET programming for database, event log testing, and other utility development tasks
- C#/.NET, MSTest, and XML usage for test case automation
- Visual Studio Team Foundation Server (TFS) for IDE and source code control
- SQL Server 2008 experiences in DB install, backup & restoration
- Investigating defects to identify true root cause and potential fixes/suggestions/improvements
- Investigating feature requirements to reduce defects in design stages
- Championing testability hook development to give clear quality measurements
- Investigating customer pain points and leveraging face to face relationships/Support calls/beta chats/usability studies to improve quality and customer satisfaction
- Considerable Confidential testing experience and excellent communication skills to support successful knowledge transfer to all cross - functional disciplines including PM/DEV/Test/Ops/Marketing/PSS/Internal Feature Partners/OEMs/ and external partners
PROFESSIONAL EXPERIENCE:
Confidential
Software Design Engineer in Test (SDET)
Responsibilities:
- Primary functional contact point for ten person test team driving Deployments, Triage (as test lead proxy), BVT, Test Pass Execution, End to End Testing, Daily/Weekly team prioritization, Team load balancing, Third party engagement and off-shore test coordination.
- Production release completed with zero errors
- 100% test coverage for all features published in test studio
- 100% automation coverage for all regression cases checked into test studio
- Zero automation bugs for the final four months of the development cycle
- Regression test passes reduced from 4 days to 1 day
- Regression testers reduced from 5 contributors to 2 contributors
- BVT and Regression Testing Ramp up reduced from one week to less than a day
- Developed common automation test libraries used by the entire test team (~20) which increased test coverage while exceeding internal automation development deadlines. Deliverables included:
- C#/ADO.NET database helper classes for testing with SQL Server 2008
- C#/.NET event log testing helper classes
- C# automated test cases using MSTest
- All automation developed in Visual Studio 2008 and TFS
- Developed setup testing strategy/tactics for internally developed product and third party financial tool which resulted in zero deployment defects during test passes and milestone release cycles.
- Authored deployment document for use by Operations, Test and Development team
- Authored and tested all setup test cases
- Internal product deployment contributors reduced from 4 to 1
- Internal product deployment ramp up reduced from 3 days to half a day
- All testers ramped up and completed an internal product deployment prior to RC phase resulting in zero down time from build completion to deployment execution
- Third party product deployment and BVT reduced from 2 days to half a day
- Third party product deployments result in zero “user error” defects
- All third party product deployment bugs published by test team were fixed and updated in third party product builds
- Test team assumed all support responsibilities for PRE-PROD testing environment supporting internal product and third party tool testing by testers and nearly fifty customers across the client’s entire business
- Deployment efficiency improved as testing increases from one 3rd party build a week to twelve
Confidential
SDET
Responsibilities:
- Developed UI Application Class library and test methods in C#. Automated all build verification test scenarios and maintained high automation quality with zero test code failures during acceptance tests automation dependency delivered to all testers enabling end to end automation (including China)
- Full build verification test efforts reduced from half a day to under an hour
- Authored test plans reviewed by all cross-functional contributors and easily repeatable acceptance cases that were handed to external teams with no ramp up required
- High basic verification quality during new feature implementation kept the test team unblocked
- External testers in China achieved efficiency by completing their install testing ahead of other features
- Domain expert for Install and sought out as lead test contributor for internal discussions with other Confidential product groups and external Original Equipment Manufacturers (OEM).
- Costly design churn avoided in several feature decisions
- Continuous acceptance testing of customer scenarios and critical-path risk management feedback beyond feature ownership areas
- High quality and efficiency ensured for test pass work and other end user testing experiences in the organization
- Lengthy Beta cycle avoided and Confidential wide testing commenced at the end of Code Complete ensuring prompt feedback on quality
- Streamlined team-wide manual testing through the use and evangelism of Confidential Virtual PC with pre-installed debugging tools.
- The test team and other contributors became more efficient at ruling out false negative conditions, isolating failure scenarios, and securing developer engagement.
- Helped the team avoid costly internal and externally requested feature changes by presenting the facts in an organized argument, by recommending solutions that better suited customer needs, and leveraging existing technologies
- Focusing on automation skills development satisfied a key team dependency and broadened ability to collaborate with teams across continents
- Learned that pro-actively providing automation collateral and support to the China testers and Search Team helped them stay efficient
Confidential
SDET
Responsibilities:
- Authored test plans and test cases of OEM Bootstrapper executable and sections of OEM Pre-Installation Kit documentation for release to OEM partner. Performed functional, acceptance and release testing of OEM deliverables
- There were zero defects at release time
- Performed IE8 integration testing by gathering cases from testers, authored new cases based on product research, manually tested new builds and gave a brown bag to the team. for this key business and product dependency
- No blocking issues were found during the development cycle
- Continuous use of debugging tools and symbols to identify crashes and exceptions prior to authoring bugs.
- Defect isolation and resolution of crashes and exceptions reduced from two days to half a day
- Provided partner team with clear documentation on internal testing tools, test collateral and wiki articles during multiple releases
- Team partners were able to complete their deliverables to our team on schedule and with high quality.
- Providing quality assurance with zero defects allowed the team to continue iterating on install development with little risk of regression despite a complete turnover in team contributors after release
- Knowledge of partner relationships, cross group coordination and install as a feature was expanded. Gained more confidence as an author of OEM documentation deliverables even with an external partner located out of state
- Expanding IE partner relationship beyond simple day to day communication allowed for quicker turnaround of defect isolation on both sides and kept both teams updated on timelines and tactical strategic moves. Ensured quality and improved efficiency on both sides
Confidential
SDET
Responsibilities:
- Developed comprehensive test plans, test cases, and end to end scenarios to cover the full customer authentication and out of box experience
- High quality at product release time with zero defects
- Developed automated test case bed in C# to achieve full Priority 0/Priority 1 test case coverage.
- Test pass completion time reduced from three days to half a day
- Coordinated cross team release management and defect analysis involving all stakeholders (internal and external) including Program Management, Development, Testing and Operations. Also coordinated partner testing integration relationships for the test team
- The product was successful released with high quality in the absence of key contributors
- Authored acceptance tests for environment integration to ensure high quality test and production environment.
- False negative defects reduced to zero during all phases of release
- Achieved full P0/P1 test case coverage by learning more about C#, the internal system deployment process, and ways to improve production and test deployment efficiency
- Developed cross group leadership skills with an external partner for the first time. Became better educated on functional flow design and gained confidence as a lead contributor by working with partners out of state
- Learned that engineering quality and credibility in the team must succeed even when the business need for the product falters. These efforts gained our team enough credibility to earn and win the toolbar charter for the company
Confidential
SDET
Responsibilities:
- Co-designed harness to automate UI test cases in C#. Developed all code samples and knowledge transfer collateral to help the test team ramp up and contribute to automation. Educated all testers face to face on automation setup, framework how-to’s, and efficient test case automation development
- Individual contributors and leads began contributing to automation efforts for the first time
- Test pass completion time reduced from one week to half a day
- Exceeded expectations on bug finding rates. Authored well written bugs and feature suggestions. Assigned to mentor individual contributors on bug authoring and advocate strong quality in triage.
- Triage team reported improved quality in team bugs
- Educated product support team on architecture, design and operation issues in our internet access delivery
- Churn rate of customers significantly declines
- Participated in functional flow development discussions, UI discussions, customer support exercises on campus and in call centers, beta chat sessions with customers, and all team wide customer QOS initiatives
- Customer satisfaction scores went up by 15%
- Designated substitute for my managers during release management, QFE planning, bug triages, feature discussions and fire drills
- The product was successful released with high quality in the absence of key contributors
- Developed comprehensive test plans, test cases, and end to end scenarios to cover the full customer authentication and out of box experience
- High quality at product release time with zero defects
- Individual contributor on Dialup access client software, Dialup compression client software, Wi-Fi access client software and broadband access products supporting MSN Internet Access business charters in scrum and waterfall projects
- Developed comfort with JIT products that require “Always up” maintenance and support
- Product cycles reduced from 1.5 years to 4 months as team embraced faster development processes, stronger communication, and more accountability
- Got face to face with customers in focus groups and home visits. Transferred their feedback into test cases and new requirements to improve customer value
- Became “go-to guy” for critiquing and assessing UI flows, error messaging and release notes
