Lesson overview. Lesson 7 Version Management and Testing. Testing - The V model. How to test. Testing and Coding. Modeling and Testing.

Size: px

Start display at page:

Download "Lesson overview. Lesson 7 Version Management and Testing. Testing - The V model. How to test. Testing and Coding. Modeling and Testing."

Clement Skinner
6 years ago
Views:

1 Lesson overview Lesson 7 Version Management and Testing Rikard Land rikard.land@mdh.se (Some slides by Andreas Sjögren) Testing JUnit SCM (Software Configuration Management) Subversion & Tortoise We will also touch upon security SSH & PuTTY 1 2 Testing - The V model How to test Requirements Engineering High Level Design Acceptance Test Integration Test Debugging is manual work Takes time Occupies a person (waste of resources) Easy to omit something Detailed Design Implementation Unit Test Compilation time Automated testing desirable! Acceptance test Not possible Static code check (compilation) - Yes Unit test Yes In between at least some help from computers 3 4 Testing and Coding Modeling and Testing Recently, a number of aggressive approaches: Write test cases before you write the code (or at least immediately after) All tests should (ideally) be run after each change If some tests fail, immediately correct the code (Regression testing) Can the software be implemented to be easily testable? What we certainly have to do is implement the system After that, test it To make sure implementation is OK Before that, model it To make sure implementation will be OK Testing cannot replace modeling You can never have full coverage Tests may contain bugs We want to know earlier than after implementation! 5 6 1

2 Attitude JUnit and Automated Unit Testing We test to find errors! not to show that there are no errors We want to find (and remove) errors by provoking failures (and catch them systematically) Error = fault latent in the code Failure = erroneous behavior in runtime Some people claim that: Programmers should not write tests for their own code The best programmers should write tests Requirements (!) on testing software: Easy to add tests Smart automation/integration with development tools: Easy to run all tests Easy to define and run a subset Context dependence/independence? Clear information about success/failure Easy to track errors/failures to code Resource efficient 7 8 JUnit and Automated Unit Testing Example Each test should test one thing To know exactly what went wrong The name of the test should tell what is tested For some input: Test that the normal case works Test that the application detects exceptions (a little more complex tests, but provokes defensive programming ) Code to be tested: Class X { public float average(float[] nums) { float avg; Test code: for () { return avg; public void testaverage() { float avg[] = [1,3,8,6,3,9]; assertequal(x.average(avg),5); 9 10 SCM / Version management Version Management SCM = Software Configuration Management During a development project it is important to keep track of different parts, and changes to these parts Source code Requirements, design models Documents Web pages SCM responsible 22 Item A Ver 0 Ver 1 Ver 2 Ver3 Item B Ver 0 Ver 1 Item C Ver 0 Ver 1 Ver 2 Build/make Baseline A Products Baseline B (Subversion: tag A ) (Subversion: tag B ) 23 2

Versioned Files Subversion Files includes several versions, placed in a repository Check In (Subversion: commit ) Check Out (Subversion: checkout, update ) RCS,v Version 1.1 1.

3 Versioned Files Subversion Files includes several versions, placed in a repository Check In (Subversion: commit ) Check Out (Subversion: checkout, update ) RCS,v Version Open source tool Based on older CVS (Concurrent Versions System) Originally developed for the UNIX platform, based on the older RCS Versions for different platforms Repository stored on the server Users keep local copies of files on their local workspaces (e.g. local hard drive) Several client tools (with graphical user interfaces) developed for it Subversion important user commands Subversion Locking Server Local Checkout (first time) Update (from repository) Updates existing files and checks out new files Local Server Add Adds a new file to repository, needs commit Adds a directory to repository, needs commit Commit ( check in ) Subversion uses optimistic locking Any number of users can edit a file Conflicts may arise when committing the changes Merge possible (within Subversion) Makes less sense when working with binary files Cannot be merged (by Subversion) Pessimistic locking is more appropriate in some circumstances Tortoise Tortoise is a client for Subversion (and other SCM systems) Integrated with Windows Explorer Right-click commands Icons on all files (can be a little slow to update)

34 35 Security This is a distributed system Utilizing

SSH) So the client must also use these methods SSH Authentication mechanisms Username / password Public / private keys Many things to keep in mind Directories and files

Follow the instructions in the lab (and try to understand them) The focus of the lab is testing and using SCM correctly 36 37 Lab Environment Subversion server already

4 34 35 Security This is a distributed system Utilizing computers to which others also have access Secure communication Server allows only certain access methods (e.g. SSH) So the client must also use these methods SSH Authentication mechanisms Username / password Public / private keys Many things to keep in mind Directories and files with different access rights Keep passwords and private keys private! Follow the instructions in the lab (and try to understand them) The focus of the lab is testing and using SCM correctly Lab Environment Subversion server already set up for you! Subversion client: Tortoise You need to provide some settings SSH client: PuTTY You need to provide some settings SSH_Client privatekey connect(username,password) connect(privatekey) SSH_Protocol Subversion_Client add() update() commit() use_settings plugin <<artifact>> SSH_Settings Windows_Explorer SSH_Server read_write <<artifact>> Subversion_Repository Passive repository (File structure) executecommand(command) 38 4

5 Assignment 7 a7.html 41 5

Task-Oriented Solutions to Over 175 Common Problems. Covers. Eclipse 3.0. Eclipse CookbookTM. Steve Holzner

Task-Oriented Solutions to Over 175 Common Problems Covers Eclipse 3.0 Eclipse CookbookTM Steve Holzner Chapter CHAPTER 6 6 Using Eclipse in Teams 6.0 Introduction Professional developers frequently work