How to test a weekly crontab job on Linux?

In order to test a crontab job we first need to explore and understand what a crontab job is.

A crontab job is nothing but a list of commands that we can run during a cron job. A cron job is a utility that schedules automatic execution of commands at specific times.

We can start a cron job with the help of bash script by following the commands shown below −

crontab -e

This will open a file which you can edit, insert the cron job shell script in the above file and then close that file.

Just insert the code shown below in the above file

* * * * * sample.sh

The above command contains 5 *, where each * indicates the time and then follows the script. We have the script which we want to run as a cron job. In the sample.sh we need to write the following command to make the environment variables available to it.

Understanding Cron Time Format

Before testing weekly cron jobs, it's important to understand the cron time format:

* * * * * command
? ? ? ? ?
? ? ? ? ???? Day of week (0-7, Sunday = 0 or 7)
? ? ? ?????? Month (1-12)
? ? ???????? Day of month (1-31)
? ?????????? Hour (0-23)
???????????? Minute (0-59)

A weekly job runs using 0 0 * * 0 (every Sunday at midnight) or similar patterns.

Method 1: Using Lock File for Testing

One way to test a weekly cron job is to make use of a lock file that when used will set the cron job to run every minute. This way you can keep editing the files and each minute these files will be tested and you will be aware if your cron job is working properly or not.

Just create a shell script for the same inside which you can place your cron job.

The shell script is shown below −

#!/bin/sh
if [ -e /tmp/lock ]
then
    echo "cronjob locked"
    exit 1
fi

touch /tmp/lock
<..do your regular cron here ...>
rm -f /tmp/lock

To test this weekly job, temporarily change the cron schedule to run every minute:

* * * * * /path/to/your/script.sh

Method 2: Monitoring Cron Logs

An alternate way is to make use of the /var/log directory and then run the following command shown below −

tailf /var/log/cron

The above command will allow you to check the cron log updates in real time. On some systems, you may need to use:

tail -f /var/log/syslog | grep CRON

Method 3: Manual Execution

You can manually execute the cron script to test its functionality before scheduling:

/path/to/your/weekly-script.sh

This helps verify that the script runs without errors and produces expected output.

Method 4: Using at Command

For immediate testing, use the at command to schedule a one-time execution:

echo "/path/to/your/script.sh" | at now + 1 minute

Best Practices for Testing

• Always test scripts manually before adding them to crontab

• Use absolute paths for commands and files in cron jobs

• Redirect output to log files for debugging: command >> /var/log/myjob.log 2>&1

• Set appropriate environment variables at the beginning of cron scripts

• Test with temporary frequent schedules before setting weekly timing

Conclusion

Testing weekly crontab jobs requires changing the schedule temporarily to run more frequently, monitoring logs in real-time, or executing scripts manually. Using lock files prevents overlapping executions, while log monitoring helps track job execution and identify issues. Always test scripts thoroughly before deploying them as weekly scheduled tasks.