<commit_before><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
   "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" []>
<chapter id="intro">
   <title>Introduction</title>

   <para>
      We believe that integration testing should be no more complex than writing a simple unit test. We created
      Arquillian to realize that goal. One of the major complaints we heard about Seam 2 testing (i.e., SeamTest) was,
      not that it wasn't possible, but that it wasn't flexible and it was difficult to setup.
   </para>
   
   <para>
      People test in a myriad of ways, which is why it's so vital that, with Arquillian (and ShrinkWrap), we have
      decomposed the problem into its essential elements. The result is a completely flexible and portable integration
      testing framework.
   </para>
   
   <section id="mission">
      <title>Mission statement</title>
      <para>
         The mission of the Arquillian project is to provide a simple mechanism to test application code inside a
         container. But the last thing Java developers want is yet another testing framework to make their life more
         complicated. That's why Arquillian integrates transparently with familiar testing frameworks (JUnit 4 and
         TestNG 5), performs runtime packaging and deployment of tests within Java EE archives and executes the tests
         inside the container. Tests can be launched using existing IDE, Ant and Maven test plugins, thus minimizing the
         burden on the developer to <!-- validate the behavior of managed and enterprise beans or POJOs that use
         enterprise services --> perform integration testing. And the environment in which the tests are run is
         pluggable, so the developer is not locked in to a proprietary testing container.
      </para>
   </section>

   <section id="overview">
      <title>Architecture overview</title>
      <para>
         Arquillian combines a unit testing framework (JUnit or TestNG), ShrinkWrap, and one or more supported target
         containers (Java EE container, servlet container, Java SE CDI environment, etc) to provide a simple, flexible
         and pluggable integration testing environment for normal test cases.<commit_msg>revise mission<commit_after><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
   "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" []>
<chapter id="intro">
   <title>Introduction</title>

   <para>
      We believe that integration testing should be no more complex than writing a simple unit test. We created
      Arquillian to realize that goal. One of the major complaints we heard about Seam 2 testing (i.e., SeamTest) was,
      not that it wasn't possible, but that it wasn't flexible and it was difficult to setup.
   </para>
   
   <para>
      People test in a myriad of ways, which is why it's so vital that, with Arquillian (and ShrinkWrap), we have
      decomposed the problem into its essential elements. The result is a completely flexible and portable integration
      testing framework.
   </para>
   
   <section id="mission">
      <title>Mission statement</title>
      <para>
         The mission of the Arquillian project is to provide a simple mechanism to test application code inside a
         container. Since the last thing Java developers want is yet another testing framework to make their life more
         complicated, Arquillian integrates transparently with familiar testing frameworks (JUnit 4 and TestNG 5) by
         performing runtime packaging and deployment of tests within Java EE archives and executing the tests inside the
         container. Tests can be launched using existing IDE, Ant and Maven test plugins, thus minimizing the burden on
         the developer to <!-- validate the behavior of managed and enterprise beans or POJOs that use enterprise
         services --> perform integration testing. And the environment in which the tests are run is pluggable, so the
         developer is not locked in to a proprietary testing container.
      </para>
   </section>

   <section id="overview">
      <title>Architecture overview</title>
      <para>
         Arquillian combines a unit testing framework (JUnit or TestNG), ShrinkWrap, and one or more supported target
         containers (Java EE container, servlet container, Java SE CDI environment, etc) to provide a simple, flexible
         and pluggable integration testing environment for normal test cases.
{'fraction_non_alphanumeric': 0.06270554702916027, 'fraction_numerical': 0.0043850032887524665, 'mean_word_length': 3.224074074074074, 'pattern_counts': {'":': 0, '<': 43, '<?xml version=': 2, '>': 43, 'https://': 0, 'lorem ipsum': 0, 'www.': 2, 'xml': 4}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '2881790', 'n_tokens_mistral': 1161, 'n_tokens_neox': 1096, 'n_words': 581}