Pen Settings

HTML

CSS

CSS Base

Vendor Prefixing

Add External Stylesheets/Pens

Any URL's added here will be added as <link>s in order, and before the CSS in the editor. You can use the CSS from another Pen by using it's URL and the proper URL extention.

+ add another resource

JavaScript

Babel includes JSX processing.

Add External Scripts/Pens

Any URL's added here will be added as <script>s in order, and run before the JavaScript in the editor. You can use the URL of any other Pen and it will include the JavaScript from that Pen.

+ add another resource

Packages

Add Packages

Search for and use JavaScript packages from npm here. By selecting a package, an import statement will be added to the top of the JavaScript editor for this package.

Behavior

Save Automatically?

If active, Pens will autosave every 30 seconds after being saved once.

Auto-Updating Preview

If enabled, the preview panel updates automatically as you code. If disabled, use the "Run" button to update.

Format on Save

If enabled, your code will be formatted when you actively save your Pen. Note: your code becomes un-folded during formatting.

Editor Settings

Code Indentation

Want to change your Syntax Highlighting theme, Fonts and more?

Visit your global Editor Settings.

HTML

              
                <script src="https://cdn.freecodecamp.org/testable-projects-fcc/v1/bundle.js"></script>

<div id = "body-div">
<div id = "left-div">
 

  
   
  <nav id = "navbar">
    <div id = "nav-div">
    <header>
      <h1 id = "TestingDocumentation">Testing Documentation</h1>
    </header>
    </div>
    
    <div id = "topics-div">
    <ul id = "TestingTopics">
      
      <hr width: 100%;>
      <li id =  "UnitTesting-li"> 
          <a href="#Unit_Testing" class = "nav-link">Unit Testing</a></li>
      <hr width: 100%;>
      <li id =  "IntegrationTesting-li"> 
          <a href="#Integration_Testing" class = "nav-link">Integration Testing</a></li>
      <hr width: 100%;>
      <li id =  "SystemTesting-li"> 
          <a href="#System_Testing" class = "nav-link">System Testing</a></li>
      <hr width: 100%;>
      <li id =  "RegressionTesting-li"> 
          <a href="#Regression_Testing" class = "nav-link">Regression Testing</a></li>
      <hr width: 100%;>
      <li id =  "E2ETesting-li"> 
          <a href="#End_2_End_Testing" class = "nav-link">End 2 End Testing</a></li>
      <hr width: 100%;>
      <li id =  "MonkeyTesting-li"> 
          <a href="#Monkey_Testing" class = "nav-link">Monkey Testing</a></li>
    <hr width: 100%;>
      
    <li id =  "UnitTesting_2-li"> 
          <a href="#Unit_Testing_2" class = "nav-link">Unit Testing 2</a></li>
      <hr width: 100%;>
      <li id =  "IntegrationTesting_2-li"> 
          <a href="#Integration_Testing_2" class = "nav-link">Integration Testing 2</a></li>
      <hr width: 100%;>
      <li id =  "SystemTesting_2-li"> 
          <a href="#System_Testing_2" class = "nav-link">System Testing 2</a></li>
      <hr width: 100%;>
      <li id =  "RegressionTesting_2-li"> 
          <a href="#Regression_Testing_2" class = "nav-link">Regression Testing 2</a></li>
      <hr width: 100%;>
      <li id =  "E2ETesting_2-li"> 
          <a href="#End_2_End_Testing_2" class = "nav-link">End 2 End Testing 2</a></li>
      <hr width: 100%;>
     <li id =  "MonkeyTesting_2-li"> 
          <a href="#Monkey_Testing_2" class = "nav-link">Monkey Testing 2</a></li>  
      
    </ul>
    </div>
    </nav>
</div>

<div id = "right-div">
  <main id = "main-doc" class = "main">
    <section id = "Unit_Testing" class = "main-section">
      <header>
      <h2 id = "UnitTesting">Unit Testing</h2>
        </header>
        <p id = "UnitTesting_Intro">
        Unit Testing is the first level of testing, usually performed by programmers on code. It requires access to code, and is performed before the code is checked in to repository.
     <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
      </section>
    
    <section id = "Integration_Testing" class = "main-section">
      <header>
      <h2 id = "IntegrationTesting">Integration Testing</h2> 
        </header>
      <p id = "IntegrationTesting_Intro">
        Integration Testing is the second level of testing, usually performed by programmers on code. It requires access to code, and is performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "System_Testing" class = "main-section">
      <header>
      <h2 id = "SystemTesting">System Testing</h2>
        </header>
      <p id = "SystemTesting_Intro">
        System Testing is the next level of testing, usually performed by functional testers. It does not require access to code, and may be performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "Regression_Testing" class = "main-section">
      <header>
      <h2 id = "RegressionTesting">Regression Testing</h2>
        </header>
      <p id = "RegressionTesting_Intro">
        Regression Testing is the final level of testing, usually performed by functional and usability testers. It does not require access to code, and is performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "End_2_End_Testing" class = "main-section">
      <header>
      <h2 id = "E2ETesting">End 2 End Testing</h2>
        </header>
      <p id = "E2ETesting_Intro">
        End 2 End Testing is usually performed by end users or consumers of the software. It does not require access to code, and is mostly performed after the code is checked in to staging repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
   
    <section id = "Monkey_Testing" class = "main-section">
      <header>
      <h2 id = "MonkeyTesting">Monkey Testing</h2>
        </header>
      <p id = "MonkeyTesting_Intro">
        Monkey Testing is an additional level of testing, usually performed by testers in order to test robustness of the programs. It does not require access to code, and is performed after the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    


<section id = "Unit_Testing_2" class = "main-section">
      <header>
      <h2 id = "UnitTesting_2">Unit Testing 2</h2>
        </header>
        <p id = "UnitTesting_2_Intro">
        Unit Testing is the first level of testing, usually performed by programmers on code. It requires access to code, and is performed before the code is checked in to repository.
     <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
      </section>
    
    <section id = "Integration_Testing_2" class = "main-section">
      <header>
      <h2 id = "IntegrationTesting_2">Integration Testing 2</h2> 
        </header>
      <p id = "IntegrationTesting_2_Intro">
        Integration Testing is the second level of testing, usually performed by programmers on code. It requires access to code, and is performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "System_Testing_2" class = "main-section">
      <header>
      <h2 id = "SystemTesting_2">System Testing 2</h2>
        </header>
      <p id = "SystemTesting_2_Intro">
        System Testing is the next level of testing, usually performed by functional testers. It does not require access to code, and may be performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "Regression_Testing_2" class = "main-section">
      <header>
      <h2 id = "RegressionTesting_2">Regression Testing 2</h2>
        </header>
      <p id = "RegressionTesting_2_Intro">
        Regression Testing is the final level of testing, usually performed by functional and usability testers. It does not require access to code, and is performed before the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
    
    <section id = "End_2_End_Testing_2" class = "main-section">
      <header>
      <h2 id = "E2ETesting_2">End 2 End Testing 2</h2>
        </header>
      <p id = "E2ETesting_2_Intro">
        End 2 End Testing is usually performed by end users or consumers of the software. It does not require access to code, and is mostly performed after the code is checked in to staging repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>
   
    <section id = "Monkey_Testing_2" class = "main-section">
      <header>
      <h2 id = "MonkeyTesting_2">Monkey Testing 2</h2>
        </header>
      <p id = "MonkeyTesting_2_Intro">
        Monkey Testing is an additional level of testing, usually performed by testers in order to test robustness of the programs. It does not require access to code, and is performed after the code is checked in to repository.
        <br>     
          This guide assumes that you have basic knowledge of at least the following:
          <ul>
            <li> What is Software Testing?</li>
            <li> Why is Software Testing required?</li>
      </ul>
        </p>
      <p>
        Sample code may look like this:
        <pre>
        <code>
        x = 2;
        y = 2;
        z = x + y;
        </code>
        </pre>
    </section>




  </main>
</div>
</div>





              
            
!

CSS

              
                #body-div{
  display: flex;
}

#left-div{
  top: 0;
  left: 0;
  width: 250px;
  min-height: 100vh;
  border-right: 1pt solid;
}

#nav-div{
  position: fixed;
  top: 0;
  left: 0;
  height: 50px;
  z-index: 5;
  width: 250px;
  background-color: lightgrey;
}

#topics-div{
  position: relative;
  top: 50px;
  width: 250px;
  padding-left: 0;
  padding-right: 0;
}

#TestingDocumentation{
  text-align: center;
  font-size: 25px;
}

#TestingTopics{
  list-style-type: none;
}

ul{
  padding-left: 0;
  padding-right: 0;
}


#right-div{
  position: fixed;
  height: 100vh;
  width: auto;
  overflow-y: scroll;
  margin: 0 0 0 250px;
  padding-left: 50px;
}

.nav-link{
  text-decoration: none;
  color: black;
  font-weight: bold;
  font-size: 18px;
  padding: 0;
}

@media only screen and (max-width: 768px) {
  body {
    background-color: lightblue;
  }
}




              
            
!

JS

              
                
              
            
!
999px

Console