DynamicArray class in C++
Observation
Array allocated and initializes capacity elements. Which sort of defeats the purpose of having a capacity. The point of using a capacity is that you should not be paying the price of calling the constructor on elements that you don't use.
Code Review
You should put your code into a namespace.

This does not seem correct.
    DynamicArray()
        : m_size(0)              // Size is zero fine.
        , m_capacity(1)          // But a capacity of 1 with no memory allocated!
                                 // I would say the capacity here is zero
                                 // as you have no room to add any elements.
        , m_array(nullptr)
    { }


You have accepted the initializer list elements by value.
    DynamicArray(std::initializer_list&lt;T&gt; elements)

So you have already made a copy of the list.
Since you have made a copy of the list the elements in the list are yours to mutate if you want to so here you could use move semantics rather than copy semantics.
        std::copy(elements.begin(), elements.end(), m_array);
        // RATHER DO THIS
        std::move(elements.begin(), elements.end(), m_array);


Normally you expect to see the move operators marked as noexcept
    DynamicArray(DynamicArray&lt;T&gt;&amp;&amp; other)

This allows certain optimizations when you use standard algorithms and containers.

Normally I write the swap function in terms of the swap method.
    friend void swap(DynamicArray&lt;T&gt;&amp; obj1, DynamicArray&lt;T&gt;&amp; obj2) noexcept
    {
        std::swap(obj1.m_size, obj2.m_size);
        std::swap(obj1.m_capacity, obj2.m_capacity);
        std::swap(obj1.m_array, obj2.m_array);
    }

    // I would write it like this:

    void swap(DynamicArray&lt;T&gt;&amp; other) noexcept
    {
        using std::swap;
        swap(m_size,     other.m_size);
        swap(m_capacity, other.m_capacity);
        swap(m_array,    other.m_array);
    }
    friend void swap(DynamicArray&lt;T&gt;&amp; lhs, DynamicArray&lt;T&gt;&amp; rhs) noexcept
    {
        lhs.swap(rhs);
    }

Now methods (like move operators) don't need to call a free function to do a swap. They simply call the method version of swap and get the same affect.

Nice try.
    // Resizes array to store n elements.
    // Guarantees strong exception safety.

Unfortunately not quite. You can not do anything that may throw while the state of the object has been mutate but not in the final state.
    void resize(int n)
    {
        T *temp = new T[n];
        m_capacity = n;                                  // Mutation here

        std::copy(m_array, m_array + m_capacity, temp);  // Throw possible here
        delete[] m_array;                                // Throw possible here.
        m_array = temp;                                  // Final mutation
    }

The way to do this is in three phases:
    void resize(int n)
    {
        // Phase 1: Make your copy.
        T *temp = new T[n];
        std::copy(m_array, m_array + m_capacity, temp);

        // Phase 2: Mutate &quot;ALL&quot; your state to final state.
        //          You can not call anything that is not `noexcept`
        //          This limits you to very basic operations.
        m_capacity = n;
        std::swap(temp, m_array);

        // Phase 3: Clean up
        delete[] temp;           // Note the swap above.
    }

Note we can simplify this:
    void resize(int n)
    {
        // Phase 1: Make your copy.
        DynamicArray  copy(*this, n);  // Private constructor
                                       // Allocates n spaces but copies size
                                       // objects from the passed item.

        // Phase 2: Mutate &quot;ALL&quot; your state to final state.
        //          You can not call anything that is not `noexcept`
        //          This limits you to very basic operations.
        //          Luckily swap method is `noexcept`
        swap(copy);

        // Phase 3: Clean up
        // the object copy's destructor will do cleanup.
    }


I am a fan of one liners for methods that are this imple.
    bool empty() const 
    {
        return m_size == 0;
    }


Its OK to have a print method. But to make it more C++ like I would also add the operator&lt;&lt; so you can stream it. This means modifying print to take a stream.
    void print(std::ostream&amp; out = std::cout) const
    {
        for (int i = 0; i &lt; m_size; i++)
        {
            out &lt;&lt; m_array[i] &lt;&lt; &quot; &quot;;
        }
        out &lt;&lt; &quot;\n&quot;;
    }
    friend std::ostream&amp; operator&lt;&lt;(std::ostream&amp; str, DynamicArray const&amp; data)
    {
        data.print(str);
        return str;
    }


In the standard library containers that use operator[] make it a non checked interface. It is the responsibility of the user to validate before calling. They add an additional checked interface at() when the user want to validate that the index is range.
    T&amp; operator[](int index)
    {
        m_check_range(index);
        return m_array[index];
    }


    // Think of this situation
    for(int loop = 0; loop &lt; dA.size(); ++loop) {
        std::cout dA[loop];
    }

    // Here we have already guaranteed that the index is within the correct
    // range but we your code still forces an additional check (that we
    // know is never going to fail).

    // If I need to check then I call the `at()`version.
    printArrayElement(std::size_t index)
    {
         std::cout &lt;&lt; dA.at(index);   // Use checked accesses
    }

Self Plug
I have a lot of other pointers in my articles about writing a vector:
https://lokiastari.com/series/