ShingoMaeda

Thanks for your reply! I understand I should use just save() lol.

I understood that case, but this situation could happen??

1. parent record save() fails. (so primary key doesn’t change.)
2. child record foreignId changes.(follows intended change of parents.id)

I think no.

I read this thread,https://stackoverflow.com/questions/57494581/laravel-save-vs-saveorfail-real-difference-in-nutshell and some code. path: vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php

    /**
     * Save the model to the database using transaction.
     *
     * @param  array  $options
     * @return bool
     *
     * @throws \Throwable
     */
    public function saveOrFail(array $options = [])
    {
        return $this->getConnection()->transaction(function () use ($options) {
            return $this->save($options);
        });
    }

And I still don't understand when to use saveOrFail().

Quick summary between two methods would be 「saveOrFail() just wraps save() in transaction.」

Usually, save() handles single model (means single record in database), so in this situation transaction means nothing.

Then when should we use saveOrFail()??

Thanks for your reply! hmm... It can’t be helped.

How to know where one method is tested efficiently.

The project I'm joining in is on operation phase.So my task is to update existing codes. In this situation I often want to know where this method is tested.

when I run test like php artisan test I want feedbacks like

this method is tested by 
project/tests/Feature/... 
and project/tests/Unit/...

One solution for this is ... Put dd() within the method

↓

Run php artisan test then test will stop where this method is tested (and I can know where).

↓

Comment out the test method. Run php artisan test

↓

Repeat above.

But this seems inefficient. Any ideas? Thanks.