{"id":3753,"date":"2026-11-11T08:18:56","date_gmt":"2026-11-11T05:18:56","guid":{"rendered":"https:\/\/niteducation.com\/resources\/?p=3753"},"modified":"2026-11-11T08:18:59","modified_gmt":"2026-11-11T05:18:59","slug":"what-is-devops","status":"publish","type":"post","link":"https:\/\/niteducation.com\/resources\/what-is-devops\/","title":{"rendered":"What Is DevOps? Beginner Guide With Examples &amp; CI\/CD"},"content":{"rendered":"\n<!-- Article 228 \u00b7 NIT Master Stylesheet v6.3 Premium required site-wide. WordPress supplies the only H1. -->\n<article class=\"nit-article nit-article--software\" itemscope itemtype=\"https:\/\/schema.org\/Article\"><meta itemprop=\"author\" content=\"Newton Institute of Technology Editorial Team\"><meta itemprop=\"dateModified\" content=\"2026-11-10\"><div class=\"nit-hero nit-hero--software\" aria-labelledby=\"nit228-headline\"><div class=\"nit-software-hero__grid\"><div class=\"nit-software-hero__copy\"><p class=\"nit-hero__eyebrow\">ICT Explained \u00b7 Beginner&#8217;s Guide<\/p><p class=\"nit-hero__title\" id=\"nit228-headline\" itemprop=\"headline\">What Is <span>DevOps?<\/span> A Beginner-Friendly Explanation<\/p><p class=\"nit-hero__summary\" itemprop=\"description\">Understand how teams plan, test, release and monitor software, then build your first automated test using Python and GitHub Actions.<\/p><div class=\"nit-badge-row\"><span class=\"nit-badge\">8 lifecycle stages<\/span><span class=\"nit-badge\">3 real-life examples<\/span><span class=\"nit-badge\">6-test CI exercise<\/span><\/div><div class=\"nit-hero__actions\"><a class=\"nit-button nit-button--primary\" href=\"#nit228-lifecycle\">Explore the lifecycle<\/a><a class=\"nit-button nit-button--secondary\" href=\"#nit228-project\">Try the practical exercise<\/a><\/div><div class=\"nit-byline\"><p>Newton Institute of Technology Editorial Team \u00b7 Updated 10 November 2026<\/p><\/div><\/div><div class=\"nit-code-window\" aria-label=\"DevOps pipeline overview\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">devops-flow.txt<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">#&nbsp;One&nbsp;small&nbsp;code&nbsp;change<\/span>\n<span class=\"nit-code-line\">plan&nbsp;\u2192&nbsp;code&nbsp;\u2192&nbsp;test<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\u2193<\/span>\n<span class=\"nit-code-line\">release&nbsp;\u2192&nbsp;deploy<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;\u2193<\/span>\n<span class=\"nit-code-line\">monitor&nbsp;\u2192&nbsp;improve<\/span><\/div><\/div><\/div><\/div><div class=\"nit-article__body\"><section class=\"nit-quick-answer\" id=\"nit228-quick\" aria-labelledby=\"nit228-quick-title\"><div class=\"nit-quick-answer__head\"><span class=\"nit-quick-answer__mark\" aria-hidden=\"true\">\u2713<\/span><div><p class=\"nit-quick-answer__label\">Quick answer<\/p><p class=\"nit-quick-answer__kicker\" id=\"nit228-quick-title\">What is DevOps in simple terms?<\/p><\/div><\/div><div class=\"nit-quick-answer__body\"><p class=\"nit-quick-answer__text\"><strong>DevOps combines software development (Dev) and IT operations (Ops) through teamwork, automation and feedback.<\/strong> It helps the people who create software work with those who deploy, maintain and monitor it. The goal is to deliver useful changes reliably and learn from the results. DevOps is an approach to working\u2014not a programming language or a single tool. <a href=\"#nit228-ref1\" aria-label=\"Reference 1\">[1]<\/a><\/p><ul class=\"nit-quick-answer__signals\"><li>Plan<\/li><li>Build<\/li><li>Test<\/li><li>Operate<\/li><li>Improve<\/li><\/ul><\/div><\/section>\n<div class=\"nit-facts-grid\" aria-label=\"Article at a glance\"><div class=\"nit-fact-card\"><span>Difficulty<\/span><strong>Beginner<\/strong><\/div><div class=\"nit-fact-card\"><span>Practical tools<\/span><strong>Python + GitHub<\/strong><\/div><div class=\"nit-fact-card\"><span>First goal<\/span><strong>6 automated tests<\/strong><\/div><\/div>\n<p>Imagine a school adds a button for downloading examination results. Someone writes the code, someone tests it, and someone makes sure the site continues working after the update. DevOps connects those responsibilities so the change can move safely from an idea to a working feature.<\/p>\n<nav class=\"nit-toc\" aria-label=\"On this page\"><h2>In this guide<\/h2><ol><li><a href=\"#nit228-meaning\">What DevOps means<\/a><\/li><li><a href=\"#nit228-importance\">Why it matters<\/a><\/li><li><a href=\"#nit228-lifecycle\">The eight stages<\/a><\/li><li><a href=\"#nit228-cicd\">CI\/CD explained<\/a><\/li><li><a href=\"#nit228-examples\">Three practical examples<\/a><\/li><li><a href=\"#nit228-tools\">Common DevOps tools<\/a><\/li><li><a href=\"#nit228-project\">Build your first CI workflow<\/a><\/li><li><a href=\"#nit228-measuring\">Measuring improvement<\/a><\/li><li><a href=\"#nit228-comparison\">Related ICT fields<\/a><\/li><li><a href=\"#nit228-learning\">Beginner learning path<\/a><\/li><li><a href=\"#nit228-mistakes\">Common mistakes<\/a><\/li><li><a href=\"#nit228-faq\">Frequently asked questions<\/a><\/li><li><a href=\"#nit228-sources\">Sources and references<\/a><\/li><li><a href=\"#nit228-register\">Register at NIT<\/a><\/li><\/ol><\/nav>\n<section id=\"nit228-meaning\" aria-labelledby=\"nit228-meaning-title\"><h2 id=\"nit228-meaning-title\">What does DevOps mean?<\/h2><p>The name combines <strong>development<\/strong> and <strong>operations<\/strong>. Developers create and improve software; operations specialists help keep applications and the systems supporting them running.<\/p><div class=\"nit-concept-grid\"><div class=\"nit-concept-card\"><h3>Development (Dev)<\/h3><p>Write code, fix bugs, create new features and test application behaviour.<\/p><\/div><div class=\"nit-concept-card\"><h3>Operations (Ops)<\/h3><p>Configure systems, monitor applications, manage changes and restore services after failures.<\/p><\/div><div class=\"nit-concept-card\"><h3>DevOps together<\/h3><p>Share responsibility for a useful change\u2014from planning through deployment, operation and improvement.<\/p><\/div><\/div><p>A developer may make a form work perfectly on a laptop, yet the form could fail on a busy server. An operations engineer may configure a dependable server, but cannot fix incorrect application logic merely through server settings. Collaboration helps the team account for both.<\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">DevOps is an approach, not a product<\/p><p>Git, GitHub Actions, Docker and other tools can support DevOps, but no single tool creates good teamwork or a reliable delivery process. <a href=\"#nit228-ref2\" aria-label=\"Reference 2\">[2]<\/a><\/p><\/div><\/section>\n<section id=\"nit228-importance\" aria-labelledby=\"nit228-importance-title\"><h2 id=\"nit228-importance-title\">Why do organizations use DevOps?<\/h2><p>Consider a school opening its online registration portal. Ten people successfully test the application, but hundreds of applicants arrive on registration day and some submissions fail. The cause could be overloaded infrastructure, a faulty configuration or a software defect.<\/p><p>A coordinated team prepares for expected traffic, tests critical functions, checks monitoring and defines recovery steps before registration begins. If something goes wrong, developers and operations staff examine evidence together.<\/p><ul class=\"nit-list\"><li><strong>Collaboration:<\/strong> people understand one another\u2019s responsibilities and solve problems together.<\/li><li><strong>Automation:<\/strong> repeatable checks are performed consistently.<\/li><li><strong>Early feedback:<\/strong> teams discover some errors sooner.<\/li><li><strong>Reliable delivery:<\/strong> releases follow documented steps.<\/li><li><strong>Continuous improvement:<\/strong> incidents and user feedback guide the next change.<\/li><\/ul><p>DevOps does not eliminate failures; it helps teams manage change and respond effectively when a failure occurs. <a href=\"#nit228-ref1\" aria-label=\"Reference 1\">[1]<\/a><a href=\"#nit228-ref2\" aria-label=\"Reference 2\">[2]<\/a><\/p><\/section>\n<section id=\"nit228-lifecycle\" aria-labelledby=\"nit228-lifecycle-title\"><h2 id=\"nit228-lifecycle-title\">How does DevOps work? The eight-stage lifecycle<\/h2><p>A school wants students to download PDF copies of their examination results. That sounds simple, but the new feature must protect private information and avoid breaking the existing site. Follow the change through a commonly taught eight-stage lifecycle. <a href=\"#nit228-ref3\" aria-label=\"Reference 3\">[3]<\/a><\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Stage<\/th><th scope=\"col\">Meaning<\/th><th scope=\"col\">School portal example<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">1. Plan<\/th><td>Agree on the requirements<\/td><td>Specify PDF download rules<\/td><\/tr><tr><th scope=\"row\">2. Code<\/th><td>Create and record changes<\/td><td>Write and commit the PDF function<\/td><\/tr><tr><th scope=\"row\">3. Build<\/th><td>Prepare software to run<\/td><td>Package the updated application<\/td><\/tr><tr><th scope=\"row\">4. Test<\/th><td>Check expected behaviour<\/td><td>Verify marks, access and downloads<\/td><\/tr><tr><th scope=\"row\">5. Release<\/th><td>Prepare an approved version<\/td><td>Review the tested update<\/td><\/tr><tr><th scope=\"row\">6. Deploy<\/th><td>Put the version into an environment<\/td><td>Update the school server<\/td><\/tr><tr><th scope=\"row\">7. Operate<\/th><td>Keep the application available<\/td><td>Maintain the live portal<\/td><\/tr><tr><th scope=\"row\">8. Monitor<\/th><td>Observe errors and performance<\/td><td>Detect failed downloads<\/td><\/tr><\/tbody><\/table><\/div><section><h3 class=\"nit-step-heading\" data-step=\"1\">Plan: define success<\/h3><p>The team agrees that each student can download only their own results, the marks are correct, the feature works on a phone and the original results page keeps working. These testable conditions are called <strong>acceptance criteria<\/strong>.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"2\">Code: create the change<\/h3><p>A developer builds the download function and records the changes using <strong>Git<\/strong>, a version-control system. The change history helps others review what was modified.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"3\">Build: prepare the application<\/h3><p>The system compiles or packages the software as necessary. A successful build shows the preparation step completed; it does not prove that all functions work correctly.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"4\">Test: check the behaviour<\/h3><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Test situation<\/th><th scope=\"col\">Expected result<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Student downloads own results<\/th><td>Correct PDF<\/td><\/tr><tr><th scope=\"row\">Student requests another person\u2019s results<\/th><td>Access denied<\/td><\/tr><tr><th scope=\"row\">Student uses a phone<\/th><td>Download works<\/td><\/tr><tr><th scope=\"row\">Student opens original results page<\/th><td>Existing function still works<\/td><\/tr><\/tbody><\/table><\/div><p>Automated checks can verify many conditions. Layout and usability may need human inspection.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"5\">Release: prepare an approved version<\/h3><p>The team reviews the changes, documents them and prepares a version for release. A version may be ready without being installed in the live environment.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"6\">Deploy: make a version available<\/h3><p><strong>Development<\/strong> is where programmers work; <strong>staging<\/strong> is where changes are checked; <strong>production<\/strong> is where real users access the service. Deploying code and switching a feature on for users can be separate actions.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"7\">Operate: support the running system<\/h3><p>The team manages configuration, backups, access and everyday technical operations.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"8\">Monitor: learn from the result<\/h3><p>If downloads fail after release, engineers inspect logs, error reports and recent changes, then correct the fault and improve the checks. A <strong>log<\/strong> is a record of events from a system.<\/p><\/section><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Remember the cycle<\/p><p>Plan \u2192 Code \u2192 Build \u2192 Test \u2192 Release \u2192 Deploy \u2192 Operate \u2192 Monitor \u2192 Improve and repeat. In practice, security, testing and collaboration happen across the whole lifecycle.<\/p><\/div><\/section>\n<section id=\"nit228-cicd\" aria-labelledby=\"nit228-cicd-title\"><h2 id=\"nit228-cicd-title\">What is CI\/CD in DevOps?<\/h2><p><strong>CI<\/strong> means <strong>Continuous Integration<\/strong>. <strong>CD<\/strong> can mean <strong>Continuous Delivery<\/strong> or <strong>Continuous Deployment<\/strong>. Although related, they are different practices. <a href=\"#nit228-ref4\" aria-label=\"Reference 4\">[4]<\/a><\/p><div class=\"nit-project-grid\"><div class=\"nit-project-card\" data-project=\"01\"><h3>Continuous integration<\/h3><p>Developers regularly combine code changes and use automated builds or tests to catch errors.<\/p><\/div><div class=\"nit-project-card\" data-project=\"02\"><h3>Continuous delivery<\/h3><p>Tested changes are kept ready for a reliable release; a human production approval may remain.<\/p><\/div><div class=\"nit-project-card\" data-project=\"03\"><h3>Continuous deployment<\/h3><p>Eligible changes are automatically deployed after the required checks and release conditions pass.<\/p><\/div><\/div><p>For example, a new school-portal feature might accidentally break the login page. An automated login test could flag the problem when developers combine their changes.<\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">A green test is not a release approval<\/p><p>A CI workflow can report the result of its checks without preventing someone from merging or deploying code. Enforcing a required check may also need branch protection, code review or release rules. <a href=\"#nit228-ref5\" aria-label=\"Reference 5\">[5]<\/a><\/p><\/div><\/section>\n<section id=\"nit228-examples\" aria-labelledby=\"nit228-examples-title\"><h2 id=\"nit228-examples-title\">Three practical DevOps examples<\/h2><p>These fictional learning scenarios illustrate three different responsibilities: updating business software, preventing a bug and recovering from a failure.<\/p><div class=\"nit-project-grid\"><div class=\"nit-project-card\" data-project=\"01\"><h3>Water-production system<\/h3><p>An update must deduct bottles, caps and labels correctly and reject insufficient stock.<\/p><\/div><div class=\"nit-project-card\" data-project=\"02\"><h3>Online stationery shop<\/h3><p>Automated tests catch an incorrect calculation before a change is approved.<\/p><\/div><div class=\"nit-project-card\" data-project=\"03\"><h3>Delivery-tracking website<\/h3><p>Monitoring and troubleshooting help restore service after a faulty deployment.<\/p><\/div><\/div><h3>Example 1: A water-production system<\/h3><p>A small facility records 500 bottle caps in stock. A production operation uses 200, leaving <strong>300 caps<\/strong>. The update should reject a request to use more caps than are available and should not deduct the same recorded production operation twice.<\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Starting stock<\/th><th scope=\"col\">Operation<\/th><th scope=\"col\">Correct outcome<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">500 caps<\/th><td>Use 200<\/td><td>300 remain<\/td><\/tr><tr><th scope=\"row\">500 caps<\/th><td>Use 500<\/td><td>0 remain<\/td><\/tr><tr><th scope=\"row\">500 caps<\/th><td>Use 600<\/td><td>Reject: insufficient stock<\/td><\/tr><tr><th scope=\"row\">500 caps<\/th><td>Repeat an already processed operation<\/td><td>Do not double-deduct<\/td><\/tr><\/tbody><\/table><\/div><p>Developers test the stock rules. Production staff then confirm the workflow remains usable after deployment, and the technical team investigates discrepancies reported during operation.<\/p><h3>Example 2: A shop calculates the wrong total<\/h3><p>Two exercise books cost KSh 50 each. The correct total is <strong>2 \u00d7 KSh 50 = KSh 100<\/strong>. A programmer accidentally changes multiplication to addition, producing <strong>50 + 2 = 52<\/strong>. A test expecting 100 fails. The team fixes the error, retests and then reviews the change.<\/p><h3>Example 3: A delivery website fails<\/h3><p>After a deployment, customers receive errors when tracking parcels. Monitoring shows an unusual increase in failed requests. Engineers inspect logs and recent changes, identify an incorrect configuration, restore service, confirm recovery and improve future checks.<\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">Why rollback needs care<\/p><p>A rollback means returning to an earlier version. If a deployment also changed stored data or database structures, reversing application code alone may not safely restore the system.<\/p><\/div><\/section>\n<section id=\"nit228-tools\" aria-labelledby=\"nit228-tools-title\"><h2 id=\"nit228-tools-title\">Which tools do DevOps teams use?<\/h2><p>Choose tools based on the task. A beginner does not need to master every technology in this table.<\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Tool<\/th><th scope=\"col\">Main purpose<\/th><th scope=\"col\">Plain-language meaning<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Git<\/th><td>Version control<\/td><td>Tracks project changes<\/td><\/tr><tr><th scope=\"row\">GitHub<\/th><td>Collaboration<\/td><td>Hosts projects and code review<\/td><\/tr><tr><th scope=\"row\">GitHub Actions<\/th><td>Automation<\/td><td>Runs checks after repository events<\/td><\/tr><tr><th scope=\"row\">Docker<\/th><td>Containers<\/td><td>Packages applications with a consistent environment<\/td><\/tr><tr><th scope=\"row\">Terraform<\/th><td>Infrastructure as Code<\/td><td>Describes infrastructure in configuration files<\/td><\/tr><tr><th scope=\"row\">Prometheus<\/th><td>Monitoring<\/td><td>Collects operational measurements<\/td><\/tr><tr><th scope=\"row\">Grafana<\/th><td>Visualization<\/td><td>Displays measurements on dashboards<\/td><\/tr><\/tbody><\/table><\/div><p>GitHub Actions and Docker are examples of tools that support testing and consistent application environments. <a href=\"#nit228-ref6\" aria-label=\"Reference 6\">[6]<\/a><a href=\"#nit228-ref7\" aria-label=\"Reference 7\">[7]<\/a><\/p><\/section>\n<section id=\"nit228-project\" aria-labelledby=\"nit228-project-title\"><h2 id=\"nit228-project-title\">Hands-on project: automate your first software tests<\/h2><p>In this activity you will create a tiny Python price calculator, write six automated tests, and watch GitHub Actions detect a deliberately broken calculation. The exercise demonstrates <strong>continuous integration<\/strong>; it does not deploy a live application. On a phone, swipe within wide code windows and tables to see the rest of each line or column.<\/p><div class=\"nit-callout nit-callout--info\"><p class=\"nit-callout__title\">You will need<\/p><p>A GitHub account, an internet connection and a web browser. You can complete the example entirely on GitHub without installing Python locally. Work only with fictional data; do not publish private records or passwords. GitHub accounts have a minimum age of 13 and any higher local legal minimum; learners who are not eligible can use a suitable teacher-supervised alternative. <a href=\"#nit228-ref12\" aria-label=\"Reference 12\">[12]<\/a><\/p><\/div><section><h3 class=\"nit-step-heading\" data-step=\"1\">Create your repository<\/h3><p>At <a href=\"https:\/\/github.com\/\" target=\"_blank\" rel=\"noopener\">github.com<\/a>, create a repository named <code>devops-beginner-shop<\/code>. Choose Public only if you are comfortable sharing practice files. Your project will contain <code>calculator.py<\/code>, <code>test_calculator.py<\/code> and <code>.github\/workflows\/tests.yml<\/code>.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"2\">Write the calculator<\/h3><p>Choose <strong>Add file \u2192 Create new file<\/strong>, name it <code>calculator.py<\/code>, enter the code and commit it.<\/p><div class=\"nit-code-window\" aria-label=\"Code example: calculator.py\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">calculator.py<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">def&nbsp;total_cost(price,&nbsp;quantity):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;type(price)&nbsp;is&nbsp;not&nbsp;int:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raise&nbsp;TypeError(&quot;Price&nbsp;must&nbsp;be&nbsp;whole&quot;)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;type(quantity)&nbsp;is&nbsp;not&nbsp;int:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raise&nbsp;TypeError(&quot;Quantity&nbsp;must&nbsp;be&nbsp;whole&quot;)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;if&nbsp;price&nbsp;&lt;&nbsp;0&nbsp;or&nbsp;quantity&nbsp;&lt;&nbsp;0:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;raise&nbsp;ValueError(&quot;Values&nbsp;cannot&nbsp;be&nbsp;negative&quot;)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;return&nbsp;price&nbsp;*&nbsp;quantity<\/span><\/div><\/div><p>The function multiplies a whole-number item price by the quantity, rejects other input types, and rejects negative values. Calling <code>total_cost(50, 2)<\/code> should produce <strong>100<\/strong>. This is a teaching calculator, not a full financial application.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"3\">Create six automated tests<\/h3><p>Create <code>test_calculator.py<\/code>, paste the test code below and commit it. Python\u2019s built-in <code>unittest<\/code> framework compares actual results with expected results. <a href=\"#nit228-ref8\" aria-label=\"Reference 8\">[8]<\/a><\/p><div class=\"nit-code-window\" aria-label=\"Code example: test_calculator.py\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">test_calculator.py<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">import&nbsp;unittest<\/span>\n<span class=\"nit-code-line\">from&nbsp;calculator&nbsp;import&nbsp;total_cost<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">class&nbsp;ShopCalculatorTests(unittest.TestCase):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_two_bottles(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.assertEqual(total_cost(50,&nbsp;2),&nbsp;100)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_zero_quantity(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.assertEqual(total_cost(50,&nbsp;0),&nbsp;0)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_zero_price(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;self.assertEqual(total_cost(0,&nbsp;4),&nbsp;0)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_negative_price(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with&nbsp;self.assertRaises(ValueError):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;total_cost(-50,&nbsp;2)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_negative_quantity(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with&nbsp;self.assertRaises(ValueError):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;total_cost(50,&nbsp;-1)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;def&nbsp;test_decimal_quantity(self):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with&nbsp;self.assertRaises(TypeError):<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;total_cost(50,&nbsp;2.5)<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">if&nbsp;__name__&nbsp;==&nbsp;&quot;__main__&quot;:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;unittest.main()<\/span><\/div><\/div><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Case<\/th><th scope=\"col\">Input<\/th><th scope=\"col\">Expected<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Ordinary purchase<\/th><td>50 \u00d7 2<\/td><td>100<\/td><\/tr><tr><th scope=\"row\">Zero quantity<\/th><td>50 \u00d7 0<\/td><td>0<\/td><\/tr><tr><th scope=\"row\">Free items<\/th><td>0 \u00d7 4<\/td><td>0<\/td><\/tr><tr><th scope=\"row\">Negative price<\/th><td>-50 and 2<\/td><td>Reject<\/td><\/tr><tr><th scope=\"row\">Negative quantity<\/th><td>50 and -1<\/td><td>Reject<\/td><\/tr><tr><th scope=\"row\">Decimal quantity<\/th><td>50 and 2.5<\/td><td>Reject<\/td><\/tr><\/tbody><\/table><\/div><\/section><section><h3 class=\"nit-step-heading\" data-step=\"4\">Create the automated workflow<\/h3><p>Create the file at the exact path <code>.github\/workflows\/tests.yml<\/code>, paste this workflow and commit it. GitHub Actions uses workflow files in this directory. <a href=\"#nit228-ref6\" aria-label=\"Reference 6\">[6]<\/a><\/p><div class=\"nit-code-window\" aria-label=\"Code example: tests.yml\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">tests.yml<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">name:&nbsp;Test&nbsp;Shop&nbsp;Calculator<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&quot;on&quot;:&nbsp;[push,&nbsp;pull_request]<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">permissions:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;contents:&nbsp;read<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">jobs:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;test:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;runs-on:&nbsp;ubuntu-latest<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;steps:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#8211;&nbsp;name:&nbsp;Get&nbsp;project&nbsp;files<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;uses:&nbsp;actions\/checkout@v7<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;persist-credentials:&nbsp;false<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#8211;&nbsp;name:&nbsp;Set&nbsp;up&nbsp;Python<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;uses:&nbsp;actions\/setup-python@v7<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;with:<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;python-version:&nbsp;&#x27;3.12&#x27;<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&#8211;&nbsp;name:&nbsp;Run&nbsp;tests&nbsp;and&nbsp;check&nbsp;discovery<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;run:&nbsp;|<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;python&nbsp;-m&nbsp;unittest&nbsp;discover&nbsp;-v<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;python&nbsp;&#8211;&nbsp;&lt;&lt;&#x27;PY&#x27;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;import&nbsp;unittest<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;suite&nbsp;=&nbsp;unittest.defaultTestLoader.discover(&#x27;.&#x27;)<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;count&nbsp;=&nbsp;suite.countTestCases()<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;assert&nbsp;count&nbsp;&gt;=&nbsp;6,&nbsp;f&#x27;Expected&nbsp;6;&nbsp;got&nbsp;{count}&#x27;<\/span>\n<span class=\"nit-code-line\">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;PY<\/span><\/div><\/div><p>The workflow checks out your repository, sets up Python 3.12, runs the tests, and then checks that at least six tests were discovered. GitHub\u2019s current checkout and Python actions document these major-version tags. <a href=\"#nit228-ref9\" aria-label=\"Reference 9\">[9]<\/a><a href=\"#nit228-ref11\" aria-label=\"Reference 11\">[11]<\/a><\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"5\">Run and inspect the result<\/h3><p>Open <strong>Actions \u2192 Test Shop Calculator \u2192 latest run \u2192 test<\/strong>. If everything is correct, you should see:<\/p><div class=\"nit-code-window\" aria-label=\"Code example: expected-output.txt\"><div class=\"nit-code-window__bar\"><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__dot\"><\/span><span class=\"nit-code-window__file\">expected-output.txt<\/span><\/div><div class=\"nit-code-window__body\"><span class=\"nit-code-line\">Ran&nbsp;6&nbsp;tests<\/span>\n<span class=\"nit-code-line\">&nbsp;<\/span>\n<span class=\"nit-code-line\">OK<\/span><\/div><\/div><p>A green result means the configured checks passed for that run. Verify the log actually says <strong>Ran 6 tests<\/strong>, not just that the job icon is green.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"6\">Deliberately break the calculation<\/h3><p>In <code>calculator.py<\/code> replace <code>return price * quantity<\/code> with <code>return price + quantity<\/code> and commit the change. Two bottles at KSh 50 each now return <strong>52<\/strong> instead of <strong>100<\/strong>. The workflow should fail, including an error like <code>AssertionError: 52 != 100<\/code>. Three tests should fail; the three validation tests should still pass.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"7\">Fix it and confirm recovery<\/h3><p>Restore <code>return price * quantity<\/code> and commit again. The tests should return to six passing checks. You have demonstrated <strong>change \u2192 test \u2192 detect \u2192 correct \u2192 retest<\/strong>.<\/p><\/section><section><h3 class=\"nit-step-heading\" data-step=\"8\">Check what happens when tests are missing<\/h3><p>If two test methods are accidentally removed, four remaining tests may pass. The added test-count check should make the job fail because fewer than six tests were discovered. A minimum count is a simple safeguard, not a substitute for reviewing which requirements are tested.<\/p><\/section><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Problem<\/th><th scope=\"col\">What to inspect<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">No workflow appears<\/th><td>Confirm the path .github\/workflows\/tests.yml<\/td><\/tr><tr><th scope=\"row\">Workflow will not start<\/th><td>Check Actions permissions and whether a trigger occurred<\/td><\/tr><tr><th scope=\"row\">Python import error<\/th><td>Check calculator.py spelling and location<\/td><\/tr><tr><th scope=\"row\">No tests found<\/th><td>Check test_calculator.py filename<\/td><\/tr><tr><th scope=\"row\">Unexpected total<\/th><td>Compare actual result with expected result<\/td><\/tr><tr><th scope=\"row\">YAML error<\/th><td>Check indentation and the workflow file<\/td><\/tr><tr><th scope=\"row\">Too few tests<\/th><td>Restore missing test methods<\/td><\/tr><\/tbody><\/table><\/div><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Try one extra challenge<\/p><p>Add a seventh test checking three items priced at KSh 40 each. The correct total is KSh 120. Change one thing, rerun the tests and read the result.<\/p><\/div><\/section>\n<section id=\"nit228-measuring\" aria-labelledby=\"nit228-measuring-title\"><h2 id=\"nit228-measuring-title\">How do teams measure DevOps improvement?<\/h2><p>Installing many tools does not prove a team is improving. A more useful question is whether software changes reach users reliably and whether failures can be corrected effectively.<\/p><p>DORA describes five software-delivery performance metrics that help teams examine throughput and instability. <a href=\"#nit228-ref10\" aria-label=\"Reference 10\">[10]<\/a><\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Metric<\/th><th scope=\"col\">What it asks<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Change lead time<\/th><td>How long from a code commit to production?<\/td><\/tr><tr><th scope=\"row\">Deployment frequency<\/th><td>How often do we deploy?<\/td><\/tr><tr><th scope=\"row\">Failed deployment recovery time<\/th><td>How quickly can we recover after a failed deployment?<\/td><\/tr><tr><th scope=\"row\">Change fail rate<\/th><td>What proportion of deployments need immediate corrective action?<\/td><\/tr><tr><th scope=\"row\">Deployment rework rate<\/th><td>What share of deployments respond unexpectedly to production incidents?<\/td><\/tr><\/tbody><\/table><\/div><p>For a beginner, the lesson is simple: <strong>shipping faster is not useful if the software repeatedly fails.<\/strong> Teams should improve delivery speed and dependability together.<\/p><\/section>\n<section id=\"nit228-comparison\" aria-labelledby=\"nit228-comparison-title\"><h2 id=\"nit228-comparison-title\">DevOps vs software development vs cloud computing<\/h2><p>The areas are related, but each has a different emphasis.<\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Field<\/th><th scope=\"col\">Main focus<\/th><th scope=\"col\">Example<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">Software development<\/th><td>Creating and maintaining applications<\/td><td>Build a school portal<\/td><\/tr><tr><th scope=\"row\">Cloud computing<\/th><td>Providing computing resources over a network<\/td><td>Host an application<\/td><\/tr><tr><th scope=\"row\">Cloud engineering<\/th><td>Designing and operating cloud infrastructure<\/td><td>Configure cloud servers<\/td><\/tr><tr><th scope=\"row\">DevOps<\/th><td>Improving software delivery and operations<\/td><td>Automate tests and monitor releases<\/td><\/tr><\/tbody><\/table><\/div><p>One person may perform several of these tasks, especially in a small organization. DevOps can also work on privately hosted or on-premises servers; public cloud hosting is not required. To learn more about application code, read NIT\u2019s <a href=\"https:\/\/niteducation.com\/resources\/what-does-a-backend-developer-do\/\">backend developer guide<\/a>.<\/p><\/section>\n<section id=\"nit228-learning\" aria-labelledby=\"nit228-learning-title\"><h2 id=\"nit228-learning-title\">Can a complete beginner learn DevOps?<\/h2><p>Yes. Start with basic computing and a small application, then add automation and operations knowledge as your understanding grows.<\/p><div class=\"nit-table-wrap\" role=\"region\" aria-label=\"Scrollable comparison table\" tabindex=\"0\"><table class=\"nit-table\"><thead><tr><th scope=\"col\">Stage<\/th><th scope=\"col\">Learn<\/th><th scope=\"col\">Practical goal<\/th><\/tr><\/thead><tbody><tr><th scope=\"row\">1. Computing<\/th><td>Files, operating systems, networking<\/td><td>Explain where an application runs<\/td><\/tr><tr><th scope=\"row\">2. Programming<\/th><td>Python, functions, errors<\/td><td>Write a small program<\/td><\/tr><tr><th scope=\"row\">3. Version control<\/th><td>Git, commits, repositories<\/td><td>Record and explain a change<\/td><\/tr><tr><th scope=\"row\">4. Automated tests<\/th><td>unittest and GitHub Actions<\/td><td>Get a passing and failing CI run<\/td><\/tr><tr><th scope=\"row\">5. Deployment<\/th><td>Servers, environments, containers<\/td><td>Run an application consistently<\/td><\/tr><tr><th scope=\"row\">6. Operations<\/th><td>Logs, monitoring, recovery<\/td><td>Diagnose and correct a simulated failure<\/td><\/tr><\/tbody><\/table><\/div><p>Programming and scripting are useful for many DevOps roles. Learn a concept, practise it and create evidence that you can explain\u2014not merely a list of tool names.<\/p><\/section>\n<section id=\"nit228-mistakes\" aria-labelledby=\"nit228-mistakes-title\"><h2 id=\"nit228-mistakes-title\">Five DevOps mistakes beginners should avoid<\/h2><ul class=\"nit-list\"><li><strong>Thinking DevOps is only about tools.<\/strong> Communication and shared responsibility matter as well.<\/li><li><strong>Automating a process you do not understand.<\/strong> Define the expected outcome before automating.<\/li><li><strong>Treating deployment as the finish line.<\/strong> Applications need monitoring and support afterward.<\/li><li><strong>Assuming passing tests mean perfection.<\/strong> A test checks only the behaviour it covers.<\/li><li><strong>Trying to learn every tool immediately.<\/strong> Begin with one small application and a useful automated check.<\/li><\/ul><\/section>\n<section id=\"nit228-faq\" aria-labelledby=\"nit228-faq-title\"><h2 id=\"nit228-faq-title\">Frequently asked questions<\/h2><div class=\"nit-faq\"><details class=\"nit-faq__item\"><summary>What is DevOps in one sentence?<\/summary><div class=\"nit-faq__answer\"><p>DevOps connects software development and operations through teamwork, automation and feedback to improve software delivery and reliability.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Is DevOps a programming language?<\/summary><div class=\"nit-faq__answer\"><p>No. It is an approach to developing, delivering and operating software. Programming and scripting often support the work.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>What is a simple example of DevOps?<\/summary><div class=\"nit-faq__answer\"><p>A team adds a website feature, runs automated tests, deploys an approved version, monitors the result and fixes any problems.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>How is DevOps different from CI\/CD?<\/summary><div class=\"nit-faq__answer\"><p>DevOps is the broader approach. CI\/CD describes specific practices for integrating, testing, preparing and deploying changes.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Is DevOps the same as Agile?<\/summary><div class=\"nit-faq__answer\"><p>No. Agile emphasizes iterative development and responding to changing needs. DevOps connects development with delivery and operations. Teams often use both.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Can DevOps work without cloud computing?<\/summary><div class=\"nit-faq__answer\"><p>Yes. The practices apply to private servers, on-premises systems, cloud environments and combinations of them.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>What is DevSecOps?<\/summary><div class=\"nit-faq__answer\"><p>DevSecOps emphasizes considering security continuously throughout development, delivery and operations.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Do DevOps engineers need to code?<\/summary><div class=\"nit-faq__answer\"><p>Scripting and programming skills are valuable for many automation and infrastructure tasks. The exact role varies by employer.<\/p><\/div><\/details><details class=\"nit-faq__item\"><summary>Can secondary-school learners start?<\/summary><div class=\"nit-faq__answer\"><p>Yes. Begin with computing fundamentals, Python, Git and small automated tests, then progress gradually.<\/p><\/div><\/details><\/div><\/section>\n<section id=\"nit228-conclusion\" aria-labelledby=\"nit228-conclusion-title\"><h2 id=\"nit228-conclusion-title\">What should you remember about DevOps?<\/h2><p>DevOps connects writing software with the work needed to test, release, operate and improve it. That includes collaboration, repeatable processes and useful feedback from real applications.<\/p><p>You have followed a school portal through the eight-stage lifecycle, explored stock and price-calculation checks, and seen how engineers can recover from a failed deployment. You also have a reproducible beginner CI project.<\/p><div class=\"nit-callout nit-callout--success\"><p class=\"nit-callout__title\">Your next practical step<\/p><p>Create the calculator, run six tests, introduce the deliberate error and correct it. Understanding what failed\u2014and proving the fix\u2014is a strong start.<\/p><\/div><\/section>\n<section id=\"nit228-sources\" class=\"nit-sources\" aria-labelledby=\"nit228-sources-title\"><h2 id=\"nit228-sources-title\">Sources and references<\/h2><ol><li id=\"nit228-ref1\"><a href=\"https:\/\/learn.microsoft.com\/en-us\/devops\/what-is-devops\" target=\"_blank\" rel=\"noopener noreferrer\">Microsoft Learn \u2014 What Is DevOps?<\/a>.<\/li><li id=\"nit228-ref2\"><a href=\"https:\/\/aws.amazon.com\/devops\/what-is-devops\/\" target=\"_blank\" rel=\"noopener noreferrer\">Amazon Web Services \u2014 What Is DevOps?<\/a>.<\/li><li id=\"nit228-ref3\"><a href=\"https:\/\/www.ibm.com\/think\/topics\/devops-lifecycle\" target=\"_blank\" rel=\"noopener noreferrer\">IBM \u2014 What Is the DevOps Lifecycle?<\/a>.<\/li><li id=\"nit228-ref4\"><a href=\"https:\/\/aws.amazon.com\/what-is\/ci-cd\/\" target=\"_blank\" rel=\"noopener noreferrer\">Amazon Web Services \u2014 What Is CI\/CD?<\/a>.<\/li><li id=\"nit228-ref5\"><a href=\"https:\/\/docs.github.com\/en\/repositories\/configuring-branches-and-merges-in-your-repository\/managing-protected-branches\/about-protected-branches\" target=\"_blank\" rel=\"noopener noreferrer\">GitHub Docs \u2014 About Protected Branches<\/a>.<\/li><li id=\"nit228-ref6\"><a href=\"https:\/\/docs.github.com\/en\/actions\/concepts\/workflows-and-actions\/workflows\" target=\"_blank\" rel=\"noopener noreferrer\">GitHub Docs \u2014 Workflows<\/a>.<\/li><li id=\"nit228-ref7\"><a href=\"https:\/\/docs.docker.com\/get-started\/docker-overview\/\" target=\"_blank\" rel=\"noopener noreferrer\">Docker Docs \u2014 Docker Overview<\/a>.<\/li><li id=\"nit228-ref8\"><a href=\"https:\/\/docs.python.org\/3\/library\/unittest.html\" target=\"_blank\" rel=\"noopener noreferrer\">Python Documentation \u2014 unittest<\/a>.<\/li><li id=\"nit228-ref9\"><a href=\"https:\/\/github.com\/actions\/setup-python\" target=\"_blank\" rel=\"noopener noreferrer\">Official GitHub Actions \u2014 checkout and setup-python<\/a>.<\/li><li id=\"nit228-ref10\"><a href=\"https:\/\/dora.dev\/guides\/dora-metrics\/\" target=\"_blank\" rel=\"noopener noreferrer\">DORA \u2014 Software Delivery Performance Metrics<\/a>.<\/li><li id=\"nit228-ref11\"><a href=\"https:\/\/github.com\/actions\/checkout\" target=\"_blank\" rel=\"noopener noreferrer\">GitHub \u2014 actions\/checkout<\/a>.<\/li><li id=\"nit228-ref12\"><a href=\"https:\/\/docs.github.com\/en\/site-policy\/github-terms\/github-terms-of-service\" target=\"_blank\" rel=\"noopener noreferrer\">GitHub Terms of Service<\/a>.<\/li><\/ol><p><strong>Technical documentation reviewed:<\/strong> 10 November 2026. Sources are linked near the claims they support.<\/p><\/section>\n<section class=\"nit-enrol\" id=\"nit228-register\" aria-labelledby=\"nit228-register-title\"><div class=\"nit-enrol__intro\"><p class=\"nit-hero__eyebrow\">Continue learning at NIT<\/p><h2 id=\"nit228-register-title\">Learn DevOps and practical ICT skills<\/h2><p>Explore software automation, testing, deployment and operations through Newton Institute of Technology&#8217;s ICT training pathways in Migori, Kenya. Our admissions team can explain current entry requirements and available intakes.<\/p><\/div><div class=\"nit-enrol__cards\"><div class=\"nit-enrol-card\"><span>Learning focus<\/span><strong>DevOps<\/strong><p>Understand continuous integration, delivery and automation.<\/p><\/div><div class=\"nit-enrol-card\"><span>Supporting skills<\/span><strong>Python + Git<\/strong><p>Build a practical computing foundation.<\/p><\/div><div class=\"nit-enrol-card\"><span>Next step<\/span><strong>Ask admissions<\/strong><p>Explore suitable programmes and current schedules.<\/p><\/div><\/div><div class=\"nit-enrol__actions\"><a class=\"nit-button nit-button--primary\" href=\"https:\/\/niteducation.com\/admissions\/\">Register for ICT training<\/a><a class=\"nit-button nit-button--light\" href=\"https:\/\/niteducation.com\/courses\/ict\">Explore ICT courses<\/a><\/div><p>Newton Institute of Technology \u00b7 Migori Town, Kenya \u00b7 +254 713 584 858 \u00b7 info@niteducation.com<\/p><\/section><\/div><\/article>\n","protected":false},"excerpt":{"rendered":"<p>ICT Explained \u00b7 Beginner&#8217;s Guide What Is DevOps? A Beginner-Friendly Explanation Understand how teams plan, test, release and monitor software, then build your first automated test using Python and GitHub Actions. 8 lifecycle stages3 real-life examples6-test CI exercise Explore the lifecycleTry the practical exercise Newton Institute of Technology Editorial Team \u00b7 Updated 10 November 2026 [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"","ast-site-content-layout":"default","site-content-style":"default","site-sidebar-style":"default","ast-global-header-display":"","ast-banner-title-visibility":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","ast-disable-related-posts":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","astra-migrate-meta-layouts":"set","ast-page-background-enabled":"default","ast-page-background-meta":{"desktop":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"ast-content-background-meta":{"desktop":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"tablet":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""},"mobile":{"background-color":"var(--ast-global-color-5)","background-image":"","background-repeat":"repeat","background-position":"center center","background-size":"auto","background-attachment":"scroll","background-type":"","background-media":"","overlay-type":"","overlay-color":"","overlay-opacity":"","overlay-gradient":""}},"footnotes":""},"categories":[30],"tags":[36,58,42,801],"class_list":["post-3753","post","type-post","status-publish","format-standard","hentry","category-ict","tag-best-ict-courses-after-kcse","tag-cyber-security-training-in-kenya","tag-software-development-course-fees-in-kenya","tag-what-is-devops"],"_links":{"self":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3753","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/comments?post=3753"}],"version-history":[{"count":1,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3753\/revisions"}],"predecessor-version":[{"id":3754,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/posts\/3753\/revisions\/3754"}],"wp:attachment":[{"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/media?parent=3753"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/categories?post=3753"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/niteducation.com\/resources\/wp-json\/wp\/v2\/tags?post=3753"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}