Software Quality in a Modern Development Team. Presented by Timothy Bauguess and Marty Lewis

Transcription

1 Software Quality in a Modern Development Team Presented by Timothy Bauguess and Marty Lewis

2 High-Quality Software Who benefits? End users Development Stakeholders

3 Components of Software Quality Structural quality Efficiency Maintainability Scalability Security Testability Functional quality Specifications Few defects User experience

4 Process Quality Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan - The Agile Manifesto

5 Agile Testing Practices Continuous Integration Test the impact of your changes as they are committed Test-driven development Create the unit test before implementation Support tools Testing frameworks Code review Version control Work tracking

6 Why do we test?

7 Iterate. Test. Deliver to end-users faster!

8 Benefits of Rapid Development Iterations

9 Test-Driven Development Paradigm Write test Write code for test Run test REPEAT UNTIL PASSING Optional refactoring Run additional system tests

10 Test-Driven Development Paradigm Benefits High code coverage Short cycle, highly compatible with Agile methodologies Test is your spec Bite-size tasks, focus on one code unit at a time Considerations Spend time up front for requirement validation But Minimize rework New, may be met with resistance to change Developer focused

11 Agile Development Methods Behavior-driven development Domain-specific language

12 Behavior-Driven Development Write tests using business readable and domain-specific language Write code to satisfy the testing condition Refactor your code to standards.

13 Agile Development Methods Behavior-driven development Domain-specific language Feature-driven development

14 Feature-Driven Development Create a platform independent model Build a feature list <action> <result> <object> Construct a schedule Design by feature Build by feature

15 Agile Development Methods Behavior-driven development Domain-specific language Feature-driven development Lean development

16 Lean Development Eliminate waste / rework Amplify learning Decide as late as possible Deliver as quickly as possible Empower the team Build integrity See the whole

17 Agile Development Methods Behavior-driven development Domain-specific language Feature-driven development Lean development Extreme programming

18 Extreme Programming Coding / Iteration Listening Unit Tests / Acceptance Tests Small Releases

19 Agile Development Methods Behavior-driven development Domain-specific language Feature-driven development Lean development Extreme programming Scrum

20 Scrum Sprints Continuous Integration User stories Meetings Sprint Planning Daily Stand Up Sprint Review Sprint Retrospective

21 User Stories Small, manageable work items As an admin, I want to approve image uploads, so I can make sure they are appropriate Intended user What the user wants Why the user wants it Acceptance Criteria Story points Velocity

22 Testing Methodologies White Box Black Box

23 Testing Methodologies White Box Testing as a developer Testing individual units Design according to parameters Data domains well tested Used to test algorithms

24 Testing Methodologies Testing as a user Internals are unknown Based on output Fully integrated Does not test algorithms Black Box

25 Testing Methodologies White Box Grey Box Black Box

26 Unit Testing Overview Tests individual units of code Typically white box testing Should be able to run in isolation from one another Aimed at covering all code paths Limited coverage of requirements Lowest resources required to maintain

27 Unit Test Platforms (.NET) NUnit xunit.net MSTest ships with Visual Studio! 1. File New Project 2. Write test 3. Execute test

28 Integration Testing Overview Tests integrated code units Functional testing Typically black box testing Who should write integration tests? If UI testing is required, automate it!

29 Integration Testing Variants Smoke testing System testing Testing completely integrated system Functionality of system as a whole Test cases and data are used Acceptance testing Purely functional requirements Ideally, final testing before deployment Real production data Can be performed by end users

30 Integration Test Platforms Selenium web CodedUI web, desktop Postman web service / API TestComplete web, desktop, mobile Appium desktop, mobile

31 Regression Testing Can be unit or integration tests Prevent regression of user-impacting issues Verify new changes meet previous requirements Always run before deploying to users

32 Improving Our Process Quality

33 Improving Our Process Quality Azure DevOps

34 Improving Our Process Quality Test repeatability project Reliable, maintainable UI automation New tools Agile methodology VSCode / Visual Studio Git Flow

35 Thanks! Who has the first question?