Постоянное тестирование интеграции

Uploaded on

Марсел Янки - доклад на SQA Days, 2-3 декабря 2011, Москва

Марсел Янки - доклад на SQA Days, 2-3 декабря 2011, Москва

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads


Total Views
On Slideshare
From Embeds
Number of Embeds



Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

    No notes for slide


  • 1. Marcel JankieSolution Architect Code Quality “Better Software Faster” International Region
  • 2. Your Environment Development DevPartner Studio DevPartner JavaTest Automation Requirements ManagementSilkTest codingST+DPS = CIT Debugging Caliber Testing & Tuning Deployment Change Management, Production Defect Tracking, ALMTest Management StarTeam / MSTFSSCTMSilk Central Test Manager
  • 3. DevPartner– Source Code Review .NET– Security Scanning .NET– Memory Analysis .NET– Debugging and Analysis (BC) .NET / C++– Performance Analysis / Compare .NET / C++– Performance Expert .NET– Coverage Analysis .NET / C++– DPJ (All the above ++ in separate pack) Java– Compare Facility– XML Reporting / Code Quality Reports– Distributed Applications – One end-to-end view
  • 4. Detect  Track  Neutralize Clean Code 5
  • 5. Next to MSTS• Full 64 bits support• In Depth Source Code Level Info: 851 rules• Structured Call Graph Information• Extreme Powerful Debugger (BoundsChecker)• .NET Memory Leak Detection• Well written Expertise in defect reports• In depth visibility in Memory Management CLR• DiskIO and NetworkIO• System Compare• Technologies evolved over the last 25 years• XML Export and Management Reporting• Distributed Capabilities• Real Agile (TP / Silk / DPS)
  • 6. Cont. Integration Testing • Complement the Continuous Integration methodology • Code analysis during automated tests • Memory and performance analysis during unit and functional testing • Code coverage analysis during unit testing and functional testing • Code inspections to uncover poor coding practices • Security inspections to detect and remediate security vulnerabilities • Management visibility into results Management Visibility Go Live Test Assets Plan Unit Test QA Test Deploy Develop Continuous Integration7
  • 7. SilkTest 2010 R2• Record and playback reliable Test scripts• Very flexible choice of scripting language• Save precious Time of Senior team members• Usable for both Developers and non Developers• Fastest playback engine in the market• SAP support• Rich set of object recognition• Non GUI Testing Capabilities 8
  • 8. Four key capabilities SilkTest: Role Specific Interfaces Visual Scripting VB.NET Scripting SilkTest Classic 4Test Silk4J Java - Eclipse Silk4NET C#/VB.NET – VS2010Programming power Ease of use
  • 9. 10
  • 10. SAP Solution Manager = ApplicationLifecycle Management for SAP 11
  • 11. Two working modes-1. Drive everything out of Solman Push out of SolMan back into SCTM 12
  • 12. 2. Work out of SCTM 13
  • 13. New in SilkTest 2010 R2• SilkTest WorkBench enhancements • Visual Scripting• Visual Tests • insert verifications for the object currently selected • the execution of VB.NET scripts from within a visual test. • insert a screen from the test application into a visual test and storyboard• VB.Net scripting • create data-driven tests• Enhanced Open Agent 4Test support• Java AWT/Swing support• Adobe Flex Version 4.x support• 64-bit Support for .NET and Windows API-based Applications • (WPF, WinForms).• Better support for custom controls • SWT, AWT/Swing, SAP, Flex, WPF, WinForms. 14
  • 14. Demo CITSub Main()Shell ("C:Program FilesMicro FocusDevPartner StudioBoundsCheckerbc.exe /BC:cpwrdemonmfilelogfilesnmfilebc.DPbcl c:cpwrdemonmfiledebugnmfile.exe")Playback.AttachTimeOut = 60Window("Application=NMFILE.EXE Caption=Namefile").Attach Attach to Namefile WindowWindow.MenuSelect "View~Customer Count" Attach to Name Select WindowWindow("Application=NMFILE.EXE ClassName=#32770 Caption=Name Select").Attach ExecuteCheck "ContentCheckNames" Button("Caption=OK").Click Attach to Info WindowWindow("Application=NMFILE.EXE ClassName=#32770 Caption=Info").Attach Button("Caption=OK").Click Attach to Namefile WindowWindow("Application=NMFILE.EXE Caption=Namefile").Attach Window.CloseEnd Sub
  • 15. Code Quality Report
  • 16. Code Quality Report
  • 17. Coverage AnalysisCode Changes • Volatility • Changed Methods • New Methods • Line Level / Method Level Information
  • 18. CodeReview• VB.NET, C#, ASP.NET• Identifies known and potential problems – Logic, Portability, Performance, Windows, Standards, Usability and .NET Portability, Security – Represents collective knowledge from Microsoft, MicroFocus and industry experts• Code Standardization: Object Naming / Variable Naming• McCabe Cyclomatic Complexity• Static Reference Graph• 575 rules• Regular Expressions Rule Manager• Integrates into .NET 2005, .NET 2008 and .NET 2010
  • 19. Testing Evolution • Conventional • Manual Testing • Ad hoc Testing • Sequential • Waterfall • Modern • Continuous • Agile • Automated • Efficient
  • 20. Proactive approach TestRequirement Develop, Test Maintain Plan Project AutomateManagement and Tune and Analyze Validate DevPartner Silk Performer StarTeam TestPartner Caliber MSTFS Silk Test SCTM MS Visual Studio / Star Team / Team Foundation Server
  • 21. •Marcel JankieDomain Specialist Code QualityMarcel.Jankie@MicroFocus.comDirect : +31 (23) 5 66 01 79Fax : +31 (23) 5 54 06 49Mobile : +31 (6) 23 94 96 87
  • 22. 23