There are mainly eight phase of STLC

1. Test Planning And Control
3. Test Analysis
4. Test Case Development
5. Test Environment Setup
6. Test Execution
7. Exit Criteria Evaluation And Reporting
8. Test Closure

• CRS (Customer Requirement Specification)
• SRS (Software Requirement Specification)
• BRS (Business Requirement Specification)
• Functional Design Documents

This phase that begins after the test planning and analysis phase is completed.  From test analysis we can understand how to test and what is the test condition.  So easily understand and develop the test case.  In This phase evaluator creates the manual / automation test scripts.  The test data is prepared in this phase the data that is used to find the defect.  The Requirement Traceability Matrix (RTM) is also ready, Because the evaluator understands tracking the test case for the particular requirement.
 

The following diagram shows the different activities that form part of Test Case Development.

•  System Admins,
• Developers
• Testers
• Sometimes users or techies with an affinity for testing.

• Internet setup
•  LAN Wi-Fi setup
• Private network setup

• Visual Studio installation
•  Windows phone emulator
• Alternatively, assigning a Windows phone to the tester.

•  Set up production jobs to copy the data to a common test environment
• All PII (Personally Identifiable Information) is modified along with other sensitive data. The PII is replaced with logically correct, but non-personal data.
• Remove data that is irrelevant to your test.

•  Blacklist: In this approach, all the data fields are left unchanged. Except those fields specified by the users.
• Whitelist: By default, this approach, anonymizes all data fields. Except for a list of fields which are allowed to be copied. A whitelisted field implies that it is okay to copy the data as it is and anonymization is not required.

•  Internet setup
• LAN Wi-Fi setup
• Private network setup

After The test plan, the development of the test case, and the configuration of the test environment are complete, and then the execution phase of the test is executed.

In This manual test / automation script phase is executed.  If any defect is detected during the execution of the test case, it will be reported to the developer through the bug tracking system. 
If any test case result is a failure than this particular test case marked as fail.

If any test case result is matched to the expected result then a particular test case marked as Pass.

If all modules  dependent are tested and any fault is detected, the particular module test case is marked as blocked, first corrects the main module fault, and then runs the associated module test case.  For example, B the module depends on the module A.

If any fault found in the module A, the test case of the module B is not executed.  First correct the fault of the module A then rerun the module A test case, If module A result of the test case is Pass then run the module B execution of the test case.

Blocked Test noticed cases are executed after the fault is corrected by the developer.

You must be thinking what is a webhook? Where it is used? What is the usage of it? And the most important why it’s used?

Webhooks are automated services, it is a way that the app can send automated messages or information to our system.

When something happens in the system then this service is fire and our system caches those services and can do according to changes in our system.

Let’s take an example of a stripe webhook

We have integrated Stripe payment gateway, we have according to payment fields in our system’s database. When our system user do the payment in stripe at that time payment is done in stripe, but now how will our system get to know about the customer has do payment or not?

When customer complete payment in stripe, it will send service(webhook) to our system which has information about customer payment detail, our system will cache this service, then our system will find that user in our system and if found then we can do payment changes in our customer detail.

Recently, we were working in a laravel app where we have a status column in multiple models. We have multiple processes going on for which we have different jobs.

Initially job status will be "Pending", then each job will take one record, change the status to "Running" and process that record, and update the status to either "Completed" or "Failed".

We have constants for each status. Something like below,

static $STATUS_PENDING = 0;
static $STATUS_RUNNING = 1;
static $STATUS_COMPLETED = 2;
static $STATUS_FAILED = 3;

And the problem is, we need to go and define the status in every model that we have (around 10+ models).

Then we have functions to update status and check the status in each model like,

public function markRunning($saveRecord = true)
{
    $this->status = static::$STATUS_RUNNING;

    if ($saveRecord) {
        $this->save();
    }
}

public function isRunning()
{
    return $this->status === static::$STATUS_RUNNING;
}

And above functions existed for each 4 status. so what we did is, we created a common StatusTrait which can be used across multiple models.

Here is the code of StatusTrait that you can find for that.

Then in each model, we use this trait. For e.g.,

class SavePdf extends Model
{
    use StatusTrait;

    .....
}

And then can use any method of trait in all the models,

...
$savePdf = new SavePdf();
$savePdf->markRunning();
...

Or we can check if the status of the model is running or not. For e.g.,

...
if ($savePdf->isRunning()) {
    // logic here
}
...

This is how we have saved tons of writing code and optimized the code. Another advantage is, we can just update the value of any status from one single place.

You can also check this kind of pattern and do something like this.

• What’s Employee Morale?
• Characteristics of Employee Morale.
• Relation between Morale & Productivity.

• Psychological concept
• Dynamic Nature
• Group phenomenon
• Reflect others

1. lack of proper training,
2. Lack of support by co-workers or leader,
3. leaders/Superior behavior with him,
4. Irresponsible Management (If we talk about It or another small service sector Irresponsible HR )
5. Ineffective Supervision
6. Restrictive norms of the informal group
7. Outdated Technology & Methods

1. fear of losing a job,
2. less availability of alternatives
3. Strict Supervision, Rules & Regulations
4. Punishment
5. Policies and strategies focus on high productivity only.

1. Lack of motivation
2. Unclear Job role
3. Lack of harmonious Superior-Subordinate relationship

1. Factor determining morale
2. Significance of high morale
3. Impact of low morale
4. Measurement of morale

Laravel Debugbar is a great package to debug laravel applications while development. But it's not just limited to debugging. You can use it to optimize the performance of your app a lot as well. Like,

• number of models loaded in a memory
• number of queries fired with timing
• memory used and more.

In short, we can have a complete view of what's going on in each request.

But the less known and use feature it gives is the Timeline tab. Where you can see how much time is taken for each request. And more than that, how much time Laravel took to boot up and how much time our other code has taken. Check the below screenshot.

Recently we came to the case, where one of our consultation clients' CRM application was taking too much time on the first load. Their developers were not able to spot a problem. They checked queries and other stuff which looked completely good. so we were not sure where the time has been spent by the application.

That's were debugbar came to rescue us. We used its measure function facility by which we can measure the time spent in each of the function wherever we want to use. It gives simply two functions startMeasure and stopMeasure to measure the time spent between these two statements.

so we can put startMeasure in the staring of function and put stopMeasure at the end of the function which will render something like this in the timeline tab.

public function searchClients($department)
{
    \Debugbar::startMeasure("searchClients");

    // logic here

    \Debugbar::stopMeasure("searchClients");

    return $result;
}

Once we put this, we get a time that searchClients is taking. Check the screenshot below,

Hope this can help you to figure out what piece of code is taking the time and you can optimize it.

Happy Optimizing :)

• Boundary Value Analysis (BVA)
• Equivalence Class Partitioning
• Decision Table based testing.
• State Transition
• Error Guessing
• Boundary Value Analysis (BVA)

1. The marginal cost assessment is based entirely on trying the boundaries between partitions. It includes maximum, minimum, internal or external barriers, typical values, and error values. It is generally seen that numerous errors occur at the obstacles of the defined input values as opposed to the center.
2. It is also known as BVA and offers a selection of test entities that train limit values. This black container test method improves equivalence partitioning. This software program trying one approach is based on the principle that if a machine works well for these exact values, it will paint error-free for all values that are between the two limits.

1. First Enter Right Number In This Text Box and Click RESET PASSWORD Button. One OTP Comes On Mobile Number.
2. To reset the secret word should experience the "OTP" framework. The first run through the client enters the right "OTP", they will be permitted to go to the secret phrase change page.
3. In the event that the client enters mistaken "OTP" unexpectedly and second, the framework will request the third time "OTP" is entered.
4. In the event that "OTP" is valid, it will be permitted to go to the secret phrase change page, in any case, if the OTP is off base the third time, Error Message Displayed Like "Your OTP has been expired!!".

• Divide by zero
• Inserting blanks in text fields
• Pressing the enter button without entering values
• Uploading files that exceed the maximum limits
• Exception null pointer.
• Invalid parameters

1. What will be the result if the cellphone number is left blank?
2. What is the result if a character other than a digit is entered?
3. What is the result if fewer than 10 digits are entered?

<link rel="stylesheet" href="https://cdnjs.cloudflare.com/ajax/libs/sweetalert/1.1.3/sweetalert.min.css">
<script src="https://cdnjs.cloudflare.com/ajax/libs/sweetalert/1.1.3/sweetalert.min.js"></script>

<script>
       let categoryUrl = '{{route('categories.index')}}';
</script>

$(document).on('click', '.delete-btn', function (event) {
            const id = $(event.currentTarget).data('id');
            swal({
                    title: 'Delete !',
                    text: 'Are you sure you want to delete this Category" ?',
                    type: 'warning',
                    showCancelButton: true,
                    closeOnConfirm: false,
                    showLoaderOnConfirm: true,
                    confirmButtonColor: '#5cb85c',
                    cancelButtonColor: '#d33',
                    cancelButtonText: 'No',
                    confirmButtonText: 'Yes',
                },
                function () {
                    $.ajax({
                url: categoryUrl + '/' + id,
                type: 'DELETE',
                DataType: 'json',
                data:{"_token": "{{ csrf_token() }}"},
                success: function(response){
                    swal({
                                title: 'Deleted!',
                                text: 'Category has been deleted.',
                                type: 'success',
                                timer: 2000,
                            });
                    $('#categoryTbl').DataTable().ajax.reload(null, false);
                },
                error: function(error){
                    swal({
                                title: 'Error!',
                                text: error.responseJSON.message,
                                type: 'error',
                                timer: 5000,
                            })    
                }
            });
                });
        });

 public function destroy($id)
    {
        $category = $this->categoryRepository->find($id);

        if (empty($category)) {
            Flash::error('Category not found');

            return $this->sendError('Category not found.');
        }

        $this->categoryRepository->delete($id);

        return $this->sendSuccess('Category deleted successfully.');
    }

• Developer use API calling retrofit, volley JSON or other tools but API response check-in postman time confusion how to creating this response model class
• So a friend in this topic I will try your confusion remove flow below all steps and 5 min inner creating a wonderful model class

• Location in the android studio:

1. Open android studio
2. Go to File
3. Go to Setting
4. Click plugin

• check the below image && click and install RoboPOJOGenerator then your android studio restart

1. Open android studio
2. Go to File
3. Select directory below the image in showing related select any one directory
4. Right-click - select New - then below showing "RoboPOJOGenerator"

1. Postman response copy
2. Paste this response in "RoboPOJOGenerator" in one black color dialog showing in android studio
3. Left top side one cursor visible on this area in paste this response
4. Select "GSON" option in "RoboPOJOGenerator"
5. Last click generate button after a few moments your model class is ready