Engine coolant system and compression testing
3) The valvetrain COOLANT SYSTEM PRESSURE TEST: The boiling point of water (coolant) RISES under pressure. It's imperative that the coolant ...
coolant leak testing with a pressure tester and baby powder
This video was made here at Iowa Lakes Community College in our Motorcycle Technology Lab. We are leak testing the cooling system on a RC51, using ...
Redneck Radiator pressure test
items you will need: bike tire tube with valve stem. hose clamps: plastic and wood. or a baby pool will work nice.. a cheap car tire pump or a ...
coolant pressure test 2.flv
VW Vanagon coolant pressure test... and more!
E38 Coolant system pressure test results
Found problem. Radiator leak.
Build Manifesto
I met a team in the recent past who were adopting automated testing. Developers would write some automated unit tests for their application code, and run them in the IDE before marking their work as complete. Testers would then write down the testing scripts for the completed software, and then manually execute those tests, recording results. An automation tester followed behind, writing automated functional tests from a growing backlog of completed manual tests.
Regularly during the day an automated build would run on the CI server – the server would dutifully report the number of unit tests that had failed. Rarely would all the unit tests pass – the team would mark a ’stable’ build if a separate smoke suite of automated functional tests would pass. If the team was lucky enough to have a stable build at the end of the day it was deployed to a test environment, and the automated functional tests would execute overnight. Any failed functional tests would be raised as ‘bug cards’ on the card wall and reprioritised.
Lots of test automation, and build servers, but was this team practicing continuous integration?
The impact of this cycle meant that developers had no confidence to make any significant changes to the codebase to improve quality. They were discouraged from working beyond the minimum required to complete their task. As the team approached a release deadline, there were fewer ‘new feature’ cards on the wall, but a growing number of ‘bug cards’. The pressure started to mount to fix the bugs as quickly as possible. All sense of sustainable pace is now gone. After the release the team schedule requires it to start on the next batch of functionality, but there’s still quite a large number of bugs hanging over from last release. Clearly ‘agile’ doesn’t work.
Stop the line
Zero tolerance is required. The automated build must be kept ‘green’ – if it’s failed, then the highest priority for the team is to make it pass again. Never report ‘% passing tests’ – only green or red.
...tercel thermostat Directory
Radiator Pressure Tester - 9 results like the Craftsman Cooling System Pressure Tester - 70888, Stant Radiator Pressure Tester, Mityvac (MITMV4506) ...
Stant radiator - 1,420 results from 139 stores, including Stant 12028 Radiator Cooling System Tester Adapter, Stant-BP Radiator Pressure Tester - 12270, 1985-1986 BMW ...
The Versa-VacTM Pressure Tester creates a vacuum, holding coolant in with little or no loss. ... A radiator cap installs on the tester to provide pressure relief. ...
Astro Pneumatic 7858 Universal Radiator Pressure Tester. Astro Pneumatic's radiator pressure tester allows you to test for overpressure in your cooling system. ...
Amazon.com: Astro Pneumatic 7858 Universal Radiator Pressure Tester: Automotive
