Lynda PHP Testing Legacy Applications
    
    File List
    
        
            
                
                    - Exercise Files/Ex_Files_PHP_Testing_LegacyApps.zip  64.5 MB
- 3.2. Why Legacy Code Can Be Hard to Test/10.Bootstrap sequences, part 2.mp4  30.4 MB
- 5.4. Testing Legacy Code/23.Building real to doubles.mp4  24.4 MB
- 2.1. What Changes When Testing Legacy Code/08.Difficult people.mp4  21.8 MB
- 5.4. Testing Legacy Code/21.Building a scenario.mp4  17.5 MB
- 2.1. What Changes When Testing Legacy Code/07.Code coverage and confidence levels.mp4  17.5 MB
- 3.2. Why Legacy Code Can Be Hard to Test/09.Bootstrap sequences, part 1.mp4  17.3 MB
- 5.4. Testing Legacy Code/22.Planning real to doubles.mp4  15.2 MB
- 5.4. Testing Legacy Code/24.Refactor your tests.mp4  15.0 MB
- 2.1. What Changes When Testing Legacy Code/06.Quick primer on test doubles.mp4  14.5 MB
- 4.3. Laying the Foundation/17.Real vs. monkey patch vs. double.mp4  12.8 MB
- 5.4. Testing Legacy Code/20.Planning a scenario.mp4  12.8 MB
- 3.2. Why Legacy Code Can Be Hard to Test/12.Difficult deployments.mp4  12.6 MB
- 5.4. Testing Legacy Code/25.Add getters and setters.mp4  12.5 MB
- 3.2. Why Legacy Code Can Be Hard to Test/13.Poor package management practices.mp4  11.7 MB
- 4.3. Laying the Foundation/16.How we decide what to test.mp4  10.8 MB
- 5.4. Testing Legacy Code/19.Identifying dependencies.mp4  10.3 MB
- 3.2. Why Legacy Code Can Be Hard to Test/11.Hard-coded dependencies.mp4  10.2 MB
- 4.3. Laying the Foundation/15.Tests as questions.mp4  9.9 MB
- 4.3. Laying the Foundation/14.Just how many tests do we need.mp4  8.0 MB
- 1.Introduction/01.Welcome.mp4  7.2 MB
- 2.1. What Changes When Testing Legacy Code/04.TDD vs. test after.mp4  6.0 MB
- 2.1. What Changes When Testing Legacy Code/05.How the tools change.mp4  5.2 MB
- 5.4. Testing Legacy Code/18.Why test a legacy application.mp4  5.2 MB
- 6.Conclusion/26.Next steps.mp4  3.4 MB
- 1.Introduction/02.What you need you to know.mp4  1.8 MB
- 1.Introduction/03.Exercise files.mp4  1.3 MB
- 3.2. Why Legacy Code Can Be Hard to Test/10.Bootstrap sequences, part 2.en.srt  18.9 KB
- 2.1. What Changes When Testing Legacy Code/08.Difficult people.en.srt  14.6 KB
- 5.4. Testing Legacy Code/23.Building real to doubles.en.srt  12.8 KB
- 3.2. Why Legacy Code Can Be Hard to Test/09.Bootstrap sequences, part 1.en.srt  12.5 KB
- 2.1. What Changes When Testing Legacy Code/07.Code coverage and confidence levels.en.srt  12.4 KB
- 5.4. Testing Legacy Code/20.Planning a scenario.en.srt  9.9 KB
- 5.4. Testing Legacy Code/21.Building a scenario.en.srt  9.8 KB
- 2.1. What Changes When Testing Legacy Code/06.Quick primer on test doubles.en.srt  9.5 KB
- 3.2. Why Legacy Code Can Be Hard to Test/12.Difficult deployments.en.srt  9.4 KB
- 4.3. Laying the Foundation/17.Real vs. monkey patch vs. double.en.srt  9.0 KB
- 3.2. Why Legacy Code Can Be Hard to Test/11.Hard-coded dependencies.en.srt  7.8 KB
- 3.2. Why Legacy Code Can Be Hard to Test/13.Poor package management practices.en.srt  7.2 KB
- 4.3. Laying the Foundation/16.How we decide what to test.en.srt  7.2 KB
- 5.4. Testing Legacy Code/25.Add getters and setters.en.srt  7.1 KB
- 5.4. Testing Legacy Code/19.Identifying dependencies.en.srt  6.9 KB
- 5.4. Testing Legacy Code/24.Refactor your tests.en.srt  6.8 KB
- 5.4. Testing Legacy Code/22.Planning real to doubles.en.srt  6.7 KB
- 4.3. Laying the Foundation/15.Tests as questions.en.srt  6.5 KB
- 4.3. Laying the Foundation/14.Just how many tests do we need.en.srt  5.9 KB
- 5.4. Testing Legacy Code/18.Why test a legacy application.en.srt  4.3 KB
- 2.1. What Changes When Testing Legacy Code/05.How the tools change.en.srt  4.0 KB
- 1.Introduction/01.Welcome.en.srt  4.0 KB
- 2.1. What Changes When Testing Legacy Code/04.TDD vs. test after.en.srt  3.8 KB
- 6.Conclusion/26.Next steps.en.srt  2.6 KB
- 1.Introduction/02.What you need you to know.en.srt  1.2 KB
- 1.Introduction/03.Exercise files.en.srt  973 bytes
 
    Download Torrent
    
    Related Resources
    
    Copyright Infringement
    
        If the content above is not authorized, please contact us via activebusinesscommunication[AT]gmail.com. Remember to include the full url in your complaint.