• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer navigation

The Geek Diary

  • OS
    • Linux
    • CentOS/RHEL
    • Solaris
    • Oracle Linux
    • VCS
  • Interview Questions
  • Database
    • oracle
    • oracle 12c
    • ASM
    • mysql
    • MariaDB
  • DevOps
    • Docker
    • Shell Scripting
  • Big Data
    • Hadoop
    • Cloudera
    • Hortonworks HDP

autopkgtest: command not found

by admin

autopkgtest is a command-line tool in Ubuntu that is used to automatically run tests on software packages. It is typically used to validate the functionality and stability of software packages before they are released or installed on a system.

autopkgtest can be used to run a wide range of tests on a package, including unit tests, integration tests, and functional tests. It can be configured to run tests on a variety of different platforms and environments, including virtual machines, containers, and bare metal systems.

If you encounter the below error while running the autopkgtest command:

autopkgtest: command not found

you will need to have the autopkgtest package installed on your Ubuntu/Debian system. You can install autopkgtest using the apt package manager:

# apt install autopkgtest

Once autopkgtest is installed, you can use it to run tests on a package by specifying the name of the package and the tests you want to run. For example, to run all the available tests on the chromium-browser package, you could use the following command:

# autopkgtest chromium-browser

For more information on using autopkgtest, you can consult the autopkgtest documentation or use the autopkgtest –help command to view a list of available options and usage examples.

# autopkgtest --help

autopkgtest Command Examples

1. Build the package in the current directory and run all tests directly on the system:

# autopkgtest -- null

2. Run a specific test for the package in the current directory:

# autopkgtest --test-name=test_name -- null

3. Download and build a specific package with `apt-get`, then run all tests:

# autopkgtest package -- null

4. Test the package in the current directory using a new root directory:

# autopkgtest -- chroot path/to/new/root

5. Test the package in the current directory without rebuilding it:

# autopkgtest --no-built-binaries -- null

Filed Under: Linux

Some more articles you might also be interested in …

  1. lsof : Most commonly used examples
  2. CentOS / RHEL : How to get the date and time of executed command in the history command output
  3. How to work with multiple java versions under Linux
  4. vgextend Command Examples in Linux
  5. findfs Command Examples in Linux
  6. CentOS / RHEL 6 : How do I find my current runlevel?
  7. partx: command not found
  8. CentOS / RHEL 7 : systemctl replacements of legacy commands service and chkconfig
  9. “Failed to Synchronize Cache For Repo ‘repo_name’, Ignoring This Repo” – CentOS/RHEL 8 error
  10. cpufreq-set Command Examples in Linux

You May Also Like

Primary Sidebar

Recent Posts

  • protonvpn-cli Command Examples in Linux
  • protonvpn-cli connect Command Examples
  • procs Command Examples in Linux
  • prlimit: command not found

© 2023 · The Geek Diary

  • Archives
  • Contact Us
  • Copyright