feedc0de/qt-creator
1
0
Fork 0
forked from qt-creator/qt-creator
Code Pull Requests Activity
Files
c20c20f01277d1d0f7e452ee6ad7fd5f2bc34f3d
qt-creator/tests/auto/qtcprocess/tst_qtcprocess.cpp

747 lines
31 KiB
C++
Raw Normal View History

Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
/****************************************************************************
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
**
Incremented year in copyright info Change-Id: Ib5423fdd064e4546f848c0b640b0ed0514c26d3a Reviewed-by: Leena Miettinen <riitta-leena.miettinen@digia.com> Reviewed-by: Kai Koehne <kai.koehne@digia.com>
2014-01-07 13:27:11 +01:00
** Copyright (C) 2014 Digia Plc and/or its subsidiary(-ies).
Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
** Contact: http://www.qt-project.org/legal
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
**
Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
** This file is part of Qt Creator.
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
**
Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
** Commercial License Usage
** Licensees holding valid commercial Qt licenses may use this file in
** accordance with the commercial license agreement provided with the
** Software or, alternatively, in accordance with the terms contained in
** a written agreement between you and Digia. For licensing terms and
** conditions see http://qt.digia.com/licensing. For further information
** use the contact form at http://qt.digia.com/contact-us.
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
**
** GNU Lesser General Public License Usage
Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
** Alternatively, this file may be used under the terms of the GNU Lesser
** General Public License version 2.1 as published by the Free Software
** Foundation and appearing in the file LICENSE.LGPL included in the
** packaging of this file. Please review the following information to
** ensure the GNU Lesser General Public License version 2.1 requirements
** will be met: http://www.gnu.org/licenses/old-licenses/lgpl-2.1.html.
**
** In addition, as a special exception, Digia gives you certain additional
** rights. These rights are described in the Digia Qt LGPL Exception
License headers, part 2
2010-12-17 17:14:20 +01:00
** version 1.1, included in the file LGPL_EXCEPTION.txt in this package.
**
Adjust license headers Change-Id: Ice592c6de9951ee3b2c4cb52ed0bb3b6770e0825 Reviewed-by: Eike Ziller <eike.ziller@digia.com>
2012-10-02 09:12:39 +02:00
****************************************************************************/
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
#include <utils/qtcprocess.h>
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
#include <utils/hostosinfo.h>
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
#include <utils/stringutils.h>
#include <utils/environment.h>
Removed module names from #include directives. Getting the #include directives ready for Qt5. This includes the new-project wizards. Change-Id: Ia9261f1e8faec06b9285b694d2b7e9a095978d2b Reviewed-by: Eike Ziller <eike.ziller@nokia.com>
2012-02-15 10:42:41 +01:00
#include <QtTest>
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
using namespace Utils;
Fix tests build Change-Id: Ia3b9c3e30b7d5e62413d1f8c477e5a68b9c90e50 Reviewed-by: hjk <hjk121@nokiamail.com>
2014-06-26 15:03:22 +04:00
class MacroMapExpander : public AbstractMacroExpander {
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
public:
virtual bool resolveMacro(const QString &name, QString *ret)
{
QHash<QString, QString>::const_iterator it = m_map.constFind(name);
if (it != m_map.constEnd()) {
*ret = it.value();
return true;
}
return false;
}
void insert(const QString &key, const QString &value) { m_map.insert(key, value); }
private:
QHash<QString, QString> m_map;
};
class tst_QtcProcess : public QObject
{
Q_OBJECT
private slots:
void initTestCase();
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
void splitArgs_data();
void splitArgs();
void prepareArgs_data();
void prepareArgs();
void prepareArgsEnv_data();
void prepareArgsEnv();
void expandMacros_data();
void expandMacros();
void iterations_data();
void iterations();
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
void iteratorEditsWindows();
void iteratorEditsLinux();
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
private:
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
void iteratorEditsHelper(OsType osType);
Environment envWindows;
Environment envLinux;
MacroMapExpander mxWin;
MacroMapExpander mxUnix;
support tilde expansion under unix Task-number: QTCREATORBUG-4239
2011-03-28 14:50:32 +02:00
QString homeStr;
QString home;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
void tst_QtcProcess::initTestCase()
{
support tilde expansion under unix Task-number: QTCREATORBUG-4239
2011-03-28 14:50:32 +02:00
homeStr = QLatin1String("@HOME@");
home = QDir::homePath();
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QStringList env;
env << "empty=" << "word=hi" << "words=hi ho" << "spacedwords= hi ho sucker ";
envWindows = Environment(env, OsTypeWindows);
envLinux = Environment(env, OsTypeLinux);
mxWin.insert("a", "hi");
mxWin.insert("aa", "hi ho");
mxWin.insert("b", "h\\i");
mxWin.insert("c", "\\hi");
mxWin.insert("d", "hi\\");
mxWin.insert("ba", "h\\i ho");
mxWin.insert("ca", "\\hi ho");
mxWin.insert("da", "hi ho\\");
mxWin.insert("e", "h\"i");
mxWin.insert("f", "\"hi");
mxWin.insert("g", "hi\"");
mxWin.insert("h", "h\\\"i");
mxWin.insert("i", "\\\"hi");
mxWin.insert("j", "hi\\\"");
mxWin.insert("k", "&special;");
mxWin.insert("x", "\\");
mxWin.insert("y", "\"");
mxWin.insert("z", "");
mxUnix.insert("a", "hi");
mxUnix.insert("b", "hi ho");
mxUnix.insert("c", "&special;");
mxUnix.insert("d", "h\\i");
mxUnix.insert("e", "h\"i");
mxUnix.insert("f", "h'i");
mxUnix.insert("z", "");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
Q_DECLARE_METATYPE(QtcProcess::SplitError)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
Q_DECLARE_METATYPE(Utils::OsType)
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
void tst_QtcProcess::splitArgs_data()
{
QTest::addColumn<QString>("in");
QTest::addColumn<QString>("out");
QTest::addColumn<QtcProcess::SplitError>("err");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QTest::addColumn<Utils::OsType>("os");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
static const struct {
const char * const in;
const char * const out;
const QtcProcess::SplitError err;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
const OsType os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
} vals[] = {
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ "", "", QtcProcess::SplitOk, OsTypeWindows },
{ " ", "", QtcProcess::SplitOk, OsTypeWindows },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeWindows },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ " hi ho ", "hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi ho\" \"hi\" ho ", "\"hi ho\" hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "\\", "\\", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\"", "\"\"\\^\"\"\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi\"\"\"ho\"", "\"hi\"\\^\"\"ho\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\\\\\"", "\"\"\\\\\\^\"\"\"", QtcProcess::SplitOk, OsTypeWindows },
{ " ^^ ", "\"^^\"", QtcProcess::SplitOk, OsTypeWindows },
{ "hi\"", "", QtcProcess::BadQuoting, OsTypeWindows },
{ "hi\"dood", "", QtcProcess::BadQuoting, OsTypeWindows },
{ "%var%", "%var%", QtcProcess::SplitOk, OsTypeWindows },
{ "", "", QtcProcess::SplitOk, OsTypeLinux },
{ " ", "", QtcProcess::SplitOk, OsTypeLinux },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " hi ho ", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ "'hi ho' \"hi\" ho ", "'hi ho' hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " \\ ", "' '", QtcProcess::SplitOk, OsTypeLinux },
{ " \\\" ", "'\"'", QtcProcess::SplitOk, OsTypeLinux },
{ " '\"' ", "'\"'", QtcProcess::SplitOk, OsTypeLinux },
{ " \"\\\"\" ", "'\"'", QtcProcess::SplitOk, OsTypeLinux },
{ "hi'", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "hi\"dood", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "$var", "'$var'", QtcProcess::SplitOk, OsTypeLinux },
{ "~", "@HOME@", QtcProcess::SplitOk, OsTypeLinux },
{ "~ foo", "@HOME@ foo", QtcProcess::SplitOk, OsTypeLinux },
{ "foo ~", "foo @HOME@", QtcProcess::SplitOk, OsTypeLinux },
{ "~/foo", "@HOME@/foo", QtcProcess::SplitOk, OsTypeLinux },
{ "~foo", "'~foo'", QtcProcess::SplitOk, OsTypeLinux }
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
for (unsigned i = 0; i < sizeof(vals)/sizeof(vals[0]); i++) {
QString out = QString::fromLatin1(vals[i].out);
if (vals[i].os == OsTypeLinux)
out.replace(homeStr, home);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QTest::newRow(vals[i].in) << QString::fromLatin1(vals[i].in)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< out << vals[i].err << vals[i].os;
}
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
void tst_QtcProcess::splitArgs()
{
QFETCH(QString, in);
QFETCH(QString, out);
QFETCH(QtcProcess::SplitError, err);
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QFETCH(Utils::OsType, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QtcProcess::SplitError outerr;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QString outstr = QtcProcess::joinArgs(QtcProcess::splitArgs(in, os, false, &outerr), os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QCOMPARE(outerr, err);
if (err == QtcProcess::SplitOk)
QCOMPARE(outstr, out);
}
void tst_QtcProcess::prepareArgs_data()
{
QTest::addColumn<QString>("in");
QTest::addColumn<QString>("out");
QTest::addColumn<QtcProcess::SplitError>("err");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QTest::addColumn<OsType>("os");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
static const struct {
const char * const in;
const char * const out;
const QtcProcess::SplitError err;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
const OsType os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
} vals[] = {
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ " ", " ", QtcProcess::SplitOk, OsTypeWindows },
{ "", "", QtcProcess::SplitOk, OsTypeWindows },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeWindows },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ " hi ho ", " hi ho ", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi ho\" \"hi\" ho ", "\"hi ho\" \"hi\" ho ", QtcProcess::SplitOk, OsTypeWindows },
{ "\\", "\\", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\"", "\\\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi\"\"ho\"", "\"hi\"\"ho\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\\\\\"", "\\\\\\\"", QtcProcess::SplitOk, OsTypeWindows },
{ "^^", "^", QtcProcess::SplitOk, OsTypeWindows },
{ "hi\"", "hi\"", QtcProcess::SplitOk, OsTypeWindows },
{ "hi\"dood", "hi\"dood", QtcProcess::SplitOk, OsTypeWindows },
{ "%var%", "", QtcProcess::FoundMeta, OsTypeWindows },
{ "echo hi > file", "", QtcProcess::FoundMeta, OsTypeWindows },
{ "", "", QtcProcess::SplitOk, OsTypeLinux },
{ " ", "", QtcProcess::SplitOk, OsTypeLinux },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " hi ho ", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ "'hi ho' \"hi\" ho ", "'hi ho' hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " \\ ", "' '", QtcProcess::SplitOk, OsTypeLinux },
{ "hi'", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "hi\"dood", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "$var", "", QtcProcess::FoundMeta, OsTypeLinux },
{ "~", "@HOME@", QtcProcess::SplitOk, OsTypeLinux },
{ "~ foo", "@HOME@ foo", QtcProcess::SplitOk, OsTypeLinux },
{ "~/foo", "@HOME@/foo", QtcProcess::SplitOk, OsTypeLinux },
{ "~foo", "", QtcProcess::FoundMeta, OsTypeLinux }
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
for (unsigned i = 0; i < sizeof(vals)/sizeof(vals[0]); i++) {
QString out = QString::fromLatin1(vals[i].out);
if (vals[i].os == OsTypeLinux)
out.replace(homeStr, home);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QTest::newRow(vals[i].in) << QString::fromLatin1(vals[i].in)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< out << vals[i].err << vals[i].os;
}
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
void tst_QtcProcess::prepareArgs()
{
QFETCH(QString, in);
QFETCH(QString, out);
QFETCH(QtcProcess::SplitError, err);
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QFETCH(OsType, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QtcProcess::SplitError outerr;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::Arguments args = QtcProcess::prepareArgs(in, &outerr, os);
QString outstr = args.toString();
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QCOMPARE(outerr, err);
if (err == QtcProcess::SplitOk)
QCOMPARE(outstr, out);
}
void tst_QtcProcess::prepareArgsEnv_data()
{
QTest::addColumn<QString>("in");
QTest::addColumn<QString>("out");
QTest::addColumn<QtcProcess::SplitError>("err");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QTest::addColumn<OsType>("os");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
static const struct {
const char * const in;
const char * const out;
const QtcProcess::SplitError err;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
const OsType os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
} vals[] = {
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ " ", " ", QtcProcess::SplitOk, OsTypeWindows },
{ "", "", QtcProcess::SplitOk, OsTypeWindows },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeWindows },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ " hi ho ", " hi ho ", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi ho\" \"hi\" ho ", "\"hi ho\" \"hi\" ho ", QtcProcess::SplitOk, OsTypeWindows },
{ "\\", "\\", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\"", "\\\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\"hi\"\"ho\"", "\"hi\"\"ho\"", QtcProcess::SplitOk, OsTypeWindows },
{ "\\\\\\\"", "\\\\\\\"", QtcProcess::SplitOk, OsTypeWindows },
{ "^^", "^", QtcProcess::SplitOk, OsTypeWindows },
{ "hi\"", "hi\"", QtcProcess::SplitOk, OsTypeWindows },
{ "hi\"dood", "hi\"dood", QtcProcess::SplitOk, OsTypeWindows },
{ "%empty%", "%empty%", QtcProcess::SplitOk, OsTypeWindows }, // Yep, no empty variables on Windows.
{ "%word%", "hi", QtcProcess::SplitOk, OsTypeWindows },
{ " %word% ", " hi ", QtcProcess::SplitOk, OsTypeWindows },
{ "%words%", "hi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "%nonsense%words%", "%nonsensehi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "fail%nonsense%words%", "fail%nonsensehi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "%words%words%", "hi howords%", QtcProcess::SplitOk, OsTypeWindows },
{ "%words%%words%", "hi hohi ho", QtcProcess::SplitOk, OsTypeWindows },
{ "echo hi > file", "", QtcProcess::FoundMeta, OsTypeWindows },
{ "", "", QtcProcess::SplitOk, OsTypeLinux },
{ " ", "", QtcProcess::SplitOk, OsTypeLinux },
{ "hi", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ "hi ho", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " hi ho ", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ "'hi ho' \"hi\" ho ", "'hi ho' hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ " \\ ", "' '", QtcProcess::SplitOk, OsTypeLinux },
{ "hi'", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "hi\"dood", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "$empty", "", QtcProcess::SplitOk, OsTypeLinux },
{ "$word", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ " $word ", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ "${word}", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ " ${word} ", "hi", QtcProcess::SplitOk, OsTypeLinux },
{ "$words", "hi ho", QtcProcess::SplitOk, OsTypeLinux },
{ "$spacedwords", "hi ho sucker", QtcProcess::SplitOk, OsTypeLinux },
{ "hi${empty}ho", "hiho", QtcProcess::SplitOk, OsTypeLinux },
{ "hi${words}ho", "hihi hoho", QtcProcess::SplitOk, OsTypeLinux },
{ "hi${spacedwords}ho", "hi hi ho sucker ho", QtcProcess::SplitOk, OsTypeLinux },
{ "${", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "${var", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "${var ", "", QtcProcess::FoundMeta, OsTypeLinux },
{ "\"hi${words}ho\"", "'hihi hoho'", QtcProcess::SplitOk, OsTypeLinux },
{ "\"hi${spacedwords}ho\"", "'hi hi ho sucker ho'", QtcProcess::SplitOk, OsTypeLinux },
{ "\"${", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "\"${var", "", QtcProcess::BadQuoting, OsTypeLinux },
{ "\"${var ", "", QtcProcess::FoundMeta, OsTypeLinux },
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
for (unsigned i = 0; i < sizeof(vals)/sizeof(vals[0]); i++) {
QString out = QString::fromLatin1(vals[i].out);
if (vals[i].os == OsTypeLinux)
out.replace(homeStr, home);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QTest::newRow(vals[i].in) << QString::fromLatin1(vals[i].in)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< out << vals[i].err << vals[i].os;
}
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
void tst_QtcProcess::prepareArgsEnv()
{
QFETCH(QString, in);
QFETCH(QString, out);
QFETCH(QtcProcess::SplitError, err);
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QFETCH(OsType, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QtcProcess::SplitError outerr;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::Arguments args = QtcProcess::prepareArgs(in, &outerr, os, os == OsTypeLinux ? &envLinux : &envWindows);
QString outstr = args.toString();
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QCOMPARE(outerr, err);
if (err == QtcProcess::SplitOk)
QCOMPARE(outstr, out);
}
void tst_QtcProcess::expandMacros_data()
{
QTest::addColumn<QString>("in");
QTest::addColumn<QString>("out");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QTest::addColumn<OsType>("os");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QChar sp(QLatin1Char(' '));
static const struct {
const char * const in;
const char * const out;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
OsType os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
} vals[] = {
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ "plain", 0, OsTypeWindows },
{ "%{a}", "hi", OsTypeWindows },
{ "%{aa}", "\"hi ho\"", OsTypeWindows },
{ "%{b}", "h\\i", OsTypeWindows },
{ "%{c}", "\\hi", OsTypeWindows },
{ "%{d}", "hi\\", OsTypeWindows },
{ "%{ba}", "\"h\\i ho\"", OsTypeWindows },
{ "%{ca}", "\"\\hi ho\"", OsTypeWindows },
{ "%{da}", "\"hi ho\\\\\"", OsTypeWindows }, // or "\"hi ho\"\\"
{ "%{e}", "\"h\"\\^\"\"i\"", OsTypeWindows },
{ "%{f}", "\"\"\\^\"\"hi\"", OsTypeWindows },
{ "%{g}", "\"hi\"\\^\"\"\"", OsTypeWindows },
{ "%{h}", "\"h\\\\\"\\^\"\"i\"", OsTypeWindows },
{ "%{i}", "\"\\\\\"\\^\"\"hi\"", OsTypeWindows },
{ "%{j}", "\"hi\\\\\"\\^\"\"\"", OsTypeWindows },
{ "%{k}", "\"&special;\"", OsTypeWindows },
{ "%{x}", "\\", OsTypeWindows },
{ "%{y}", "\"\"\\^\"\"\"", OsTypeWindows },
{ "%{z}", "\"\"", OsTypeWindows },
{ "^%{z}%{z}", "^%{z}%{z}", OsTypeWindows }, // stupid user check
{ "quoted", 0, OsTypeWindows },
{ "\"%{a}\"", "\"hi\"", OsTypeWindows },
{ "\"%{aa}\"", "\"hi ho\"", OsTypeWindows },
{ "\"%{b}\"", "\"h\\i\"", OsTypeWindows },
{ "\"%{c}\"", "\"\\hi\"", OsTypeWindows },
{ "\"%{d}\"", "\"hi\\\\\"", OsTypeWindows },
{ "\"%{ba}\"", "\"h\\i ho\"", OsTypeWindows },
{ "\"%{ca}\"", "\"\\hi ho\"", OsTypeWindows },
{ "\"%{da}\"", "\"hi ho\\\\\"", OsTypeWindows },
{ "\"%{e}\"", "\"h\"\\^\"\"i\"", OsTypeWindows },
{ "\"%{f}\"", "\"\"\\^\"\"hi\"", OsTypeWindows },
{ "\"%{g}\"", "\"hi\"\\^\"\"\"", OsTypeWindows },
{ "\"%{h}\"", "\"h\\\\\"\\^\"\"i\"", OsTypeWindows },
{ "\"%{i}\"", "\"\\\\\"\\^\"\"hi\"", OsTypeWindows },
{ "\"%{j}\"", "\"hi\\\\\"\\^\"\"\"", OsTypeWindows },
{ "\"%{k}\"", "\"&special;\"", OsTypeWindows },
{ "\"%{x}\"", "\"\\\\\"", OsTypeWindows },
{ "\"%{y}\"", "\"\"\\^\"\"\"", OsTypeWindows },
{ "\"%{z}\"", "\"\"", OsTypeWindows },
{ "leading bs", 0, OsTypeWindows },
{ "\\%{a}", "\\hi", OsTypeWindows },
{ "\\%{aa}", "\\\\\"hi ho\"", OsTypeWindows },
{ "\\%{b}", "\\h\\i", OsTypeWindows },
{ "\\%{c}", "\\\\hi", OsTypeWindows },
{ "\\%{d}", "\\hi\\", OsTypeWindows },
{ "\\%{ba}", "\\\\\"h\\i ho\"", OsTypeWindows },
{ "\\%{ca}", "\\\\\"\\hi ho\"", OsTypeWindows },
{ "\\%{da}", "\\\\\"hi ho\\\\\"", OsTypeWindows },
{ "\\%{e}", "\\\\\"h\"\\^\"\"i\"", OsTypeWindows },
{ "\\%{f}", "\\\\\"\"\\^\"\"hi\"", OsTypeWindows },
{ "\\%{g}", "\\\\\"hi\"\\^\"\"\"", OsTypeWindows },
{ "\\%{h}", "\\\\\"h\\\\\"\\^\"\"i\"", OsTypeWindows },
{ "\\%{i}", "\\\\\"\\\\\"\\^\"\"hi\"", OsTypeWindows },
{ "\\%{j}", "\\\\\"hi\\\\\"\\^\"\"\"", OsTypeWindows },
{ "\\%{x}", "\\\\", OsTypeWindows },
{ "\\%{y}", "\\\\\"\"\\^\"\"\"", OsTypeWindows },
{ "\\%{z}", "\\", OsTypeWindows },
{ "trailing bs", 0, OsTypeWindows },
{ "%{a}\\", "hi\\", OsTypeWindows },
{ "%{aa}\\", "\"hi ho\"\\", OsTypeWindows },
{ "%{b}\\", "h\\i\\", OsTypeWindows },
{ "%{c}\\", "\\hi\\", OsTypeWindows },
{ "%{d}\\", "hi\\\\", OsTypeWindows },
{ "%{ba}\\", "\"h\\i ho\"\\", OsTypeWindows },
{ "%{ca}\\", "\"\\hi ho\"\\", OsTypeWindows },
{ "%{da}\\", "\"hi ho\\\\\"\\", OsTypeWindows },
{ "%{e}\\", "\"h\"\\^\"\"i\"\\", OsTypeWindows },
{ "%{f}\\", "\"\"\\^\"\"hi\"\\", OsTypeWindows },
{ "%{g}\\", "\"hi\"\\^\"\"\"\\", OsTypeWindows },
{ "%{h}\\", "\"h\\\\\"\\^\"\"i\"\\", OsTypeWindows },
{ "%{i}\\", "\"\\\\\"\\^\"\"hi\"\\", OsTypeWindows },
{ "%{j}\\", "\"hi\\\\\"\\^\"\"\"\\", OsTypeWindows },
{ "%{x}\\", "\\\\", OsTypeWindows },
{ "%{y}\\", "\"\"\\^\"\"\"\\", OsTypeWindows },
{ "%{z}\\", "\\", OsTypeWindows },
{ "bs-enclosed", 0, OsTypeWindows },
{ "\\%{a}\\", "\\hi\\", OsTypeWindows },
{ "\\%{aa}\\", "\\\\\"hi ho\"\\", OsTypeWindows },
{ "\\%{b}\\", "\\h\\i\\", OsTypeWindows },
{ "\\%{c}\\", "\\\\hi\\", OsTypeWindows },
{ "\\%{d}\\", "\\hi\\\\", OsTypeWindows },
{ "\\%{ba}\\", "\\\\\"h\\i ho\"\\", OsTypeWindows },
{ "\\%{ca}\\", "\\\\\"\\hi ho\"\\", OsTypeWindows },
{ "\\%{da}\\", "\\\\\"hi ho\\\\\"\\", OsTypeWindows },
{ "\\%{e}\\", "\\\\\"h\"\\^\"\"i\"\\", OsTypeWindows },
{ "\\%{f}\\", "\\\\\"\"\\^\"\"hi\"\\", OsTypeWindows },
{ "\\%{g}\\", "\\\\\"hi\"\\^\"\"\"\\", OsTypeWindows },
{ "\\%{h}\\", "\\\\\"h\\\\\"\\^\"\"i\"\\", OsTypeWindows },
{ "\\%{i}\\", "\\\\\"\\\\\"\\^\"\"hi\"\\", OsTypeWindows },
{ "\\%{j}\\", "\\\\\"hi\\\\\"\\^\"\"\"\\", OsTypeWindows },
{ "\\%{x}\\", "\\\\\\", OsTypeWindows },
{ "\\%{y}\\", "\\\\\"\"\\^\"\"\"\\", OsTypeWindows },
{ "\\%{z}\\", "\\\\", OsTypeWindows },
{ "bs-enclosed and trailing literal quote", 0, OsTypeWindows },
{ "\\%{a}\\\\\\^\"", "\\hi\\\\\\^\"", OsTypeWindows },
{ "\\%{aa}\\\\\\^\"", "\\\\\"hi ho\"\\\\\\^\"", OsTypeWindows },
{ "\\%{b}\\\\\\^\"", "\\h\\i\\\\\\^\"", OsTypeWindows },
{ "\\%{c}\\\\\\^\"", "\\\\hi\\\\\\^\"", OsTypeWindows },
{ "\\%{d}\\\\\\^\"", "\\hi\\\\\\\\\\^\"", OsTypeWindows },
{ "\\%{ba}\\\\\\^\"", "\\\\\"h\\i ho\"\\\\\\^\"", OsTypeWindows },
{ "\\%{ca}\\\\\\^\"", "\\\\\"\\hi ho\"\\\\\\^\"", OsTypeWindows },
{ "\\%{da}\\\\\\^\"", "\\\\\"hi ho\\\\\"\\\\\\^\"", OsTypeWindows },
{ "\\%{e}\\\\\\^\"", "\\\\\"h\"\\^\"\"i\"\\\\\\^\"", OsTypeWindows },
{ "\\%{f}\\\\\\^\"", "\\\\\"\"\\^\"\"hi\"\\\\\\^\"", OsTypeWindows },
{ "\\%{g}\\\\\\^\"", "\\\\\"hi\"\\^\"\"\"\\\\\\^\"", OsTypeWindows },
{ "\\%{h}\\\\\\^\"", "\\\\\"h\\\\\"\\^\"\"i\"\\\\\\^\"", OsTypeWindows },
{ "\\%{i}\\\\\\^\"", "\\\\\"\\\\\"\\^\"\"hi\"\\\\\\^\"", OsTypeWindows },
{ "\\%{j}\\\\\\^\"", "\\\\\"hi\\\\\"\\^\"\"\"\\\\\\^\"", OsTypeWindows },
{ "\\%{x}\\\\\\^\"", "\\\\\\\\\\\\\\^\"", OsTypeWindows },
{ "\\%{y}\\\\\\^\"", "\\\\\"\"\\^\"\"\"\\\\\\^\"", OsTypeWindows },
{ "\\%{z}\\\\\\^\"", "\\\\\\\\\\^\"", OsTypeWindows },
{ "bs-enclosed and trailing unclosed quote", 0, OsTypeWindows },
{ "\\%{a}\\\\\"", "\\hi\\\\\"", OsTypeWindows },
{ "\\%{aa}\\\\\"", "\\\\\"hi ho\"\\\\\"", OsTypeWindows },
{ "\\%{b}\\\\\"", "\\h\\i\\\\\"", OsTypeWindows },
{ "\\%{c}\\\\\"", "\\\\hi\\\\\"", OsTypeWindows },
{ "\\%{d}\\\\\"", "\\hi\\\\\\\\\"", OsTypeWindows },
{ "\\%{ba}\\\\\"", "\\\\\"h\\i ho\"\\\\\"", OsTypeWindows },
{ "\\%{ca}\\\\\"", "\\\\\"\\hi ho\"\\\\\"", OsTypeWindows },
{ "\\%{da}\\\\\"", "\\\\\"hi ho\\\\\"\\\\\"", OsTypeWindows },
{ "\\%{e}\\\\\"", "\\\\\"h\"\\^\"\"i\"\\\\\"", OsTypeWindows },
{ "\\%{f}\\\\\"", "\\\\\"\"\\^\"\"hi\"\\\\\"", OsTypeWindows },
{ "\\%{g}\\\\\"", "\\\\\"hi\"\\^\"\"\"\\\\\"", OsTypeWindows },
{ "\\%{h}\\\\\"", "\\\\\"h\\\\\"\\^\"\"i\"\\\\\"", OsTypeWindows },
{ "\\%{i}\\\\\"", "\\\\\"\\\\\"\\^\"\"hi\"\\\\\"", OsTypeWindows },
{ "\\%{j}\\\\\"", "\\\\\"hi\\\\\"\\^\"\"\"\\\\\"", OsTypeWindows },
{ "\\%{x}\\\\\"", "\\\\\\\\\\\\\"", OsTypeWindows },
{ "\\%{y}\\\\\"", "\\\\\"\"\\^\"\"\"\\\\\"", OsTypeWindows },
{ "\\%{z}\\\\\"", "\\\\\\\\\"", OsTypeWindows },
{ "multi-var", 0, OsTypeWindows },
{ "%{x}%{y}%{z}", "\\\\\"\"\\^\"\"\"", OsTypeWindows },
{ "%{x}%{z}%{y}%{z}", "\\\\\"\"\\^\"\"\"", OsTypeWindows },
{ "%{x}%{z}%{y}", "\\\\\"\"\\^\"\"\"", OsTypeWindows },
{ "%{x}\\^\"%{z}", "\\\\\\^\"", OsTypeWindows },
{ "%{x}%{z}\\^\"%{z}", "\\\\\\^\"", OsTypeWindows },
{ "%{x}%{z}\\^\"", "\\\\\\^\"", OsTypeWindows },
{ "%{x}\\%{z}", "\\\\", OsTypeWindows },
{ "%{x}%{z}\\%{z}", "\\\\", OsTypeWindows },
{ "%{x}%{z}\\", "\\\\", OsTypeWindows },
{ "%{aa}%{a}", "\"hi hohi\"", OsTypeWindows },
{ "%{aa}%{aa}", "\"hi hohi ho\"", OsTypeWindows },
{ "%{aa}:%{aa}", "\"hi ho\":\"hi ho\"", OsTypeWindows },
{ "hallo ^|%{aa}^|", "hallo ^|\"hi ho\"^|", OsTypeWindows },
{ "quoted multi-var", 0, OsTypeWindows },
{ "\"%{x}%{y}%{z}\"", "\"\\\\\"\\^\"\"\"", OsTypeWindows },
{ "\"%{x}%{z}%{y}%{z}\"", "\"\\\\\"\\^\"\"\"", OsTypeWindows },
{ "\"%{x}%{z}%{y}\"", "\"\\\\\"\\^\"\"\"", OsTypeWindows },
{ "\"%{x}\"^\"\"%{z}\"", "\"\\\\\"^\"\"\"", OsTypeWindows },
{ "\"%{x}%{z}\"^\"\"%{z}\"", "\"\\\\\"^\"\"\"", OsTypeWindows },
{ "\"%{x}%{z}\"^\"\"\"", "\"\\\\\"^\"\"\"", OsTypeWindows },
{ "\"%{x}\\%{z}\"", "\"\\\\\\\\\"", OsTypeWindows },
{ "\"%{x}%{z}\\%{z}\"", "\"\\\\\\\\\"", OsTypeWindows },
{ "\"%{x}%{z}\\\\\"", "\"\\\\\\\\\"", OsTypeWindows },
{ "\"%{aa}%{a}\"", "\"hi hohi\"", OsTypeWindows },
{ "\"%{aa}%{aa}\"", "\"hi hohi ho\"", OsTypeWindows },
{ "\"%{aa}:%{aa}\"", "\"hi ho:hi ho\"", OsTypeWindows },
{ "plain", 0, OsTypeLinux },
{ "%{a}", "hi", OsTypeLinux },
{ "%{b}", "'hi ho'", OsTypeLinux },
{ "%{c}", "'&special;'", OsTypeLinux },
{ "%{d}", "'h\\i'", OsTypeLinux },
{ "%{e}", "'h\"i'", OsTypeLinux },
{ "%{f}", "'h'\\''i'", OsTypeLinux },
{ "%{z}", "''", OsTypeLinux },
{ "\\%{z}%{z}", "\\%{z}%{z}", OsTypeLinux }, // stupid user check
{ "single-quoted", 0, OsTypeLinux },
{ "'%{a}'", "'hi'", OsTypeLinux },
{ "'%{b}'", "'hi ho'", OsTypeLinux },
{ "'%{c}'", "'&special;'", OsTypeLinux },
{ "'%{d}'", "'h\\i'", OsTypeLinux },
{ "'%{e}'", "'h\"i'", OsTypeLinux },
{ "'%{f}'", "'h'\\''i'", OsTypeLinux },
{ "'%{z}'", "''", OsTypeLinux },
{ "double-quoted", 0, OsTypeLinux },
{ "\"%{a}\"", "\"hi\"", OsTypeLinux },
{ "\"%{b}\"", "\"hi ho\"", OsTypeLinux },
{ "\"%{c}\"", "\"&special;\"", OsTypeLinux },
{ "\"%{d}\"", "\"h\\\\i\"", OsTypeLinux },
{ "\"%{e}\"", "\"h\\\"i\"", OsTypeLinux },
{ "\"%{f}\"", "\"h'i\"", OsTypeLinux },
{ "\"%{z}\"", "\"\"", OsTypeLinux },
{ "complex", 0, OsTypeLinux },
{ "echo \"$(echo %{a})\"", "echo \"$(echo hi)\"", OsTypeLinux },
{ "echo \"$(echo %{b})\"", "echo \"$(echo 'hi ho')\"", OsTypeLinux },
{ "echo \"$(echo \"%{a}\")\"", "echo \"$(echo \"hi\")\"", OsTypeLinux },
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
// These make no sense shell-wise, but they test expando nesting
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ "echo \"%{echo %{a}}\"", "echo \"%{echo hi}\"", OsTypeLinux },
{ "echo \"%{echo %{b}}\"", "echo \"%{echo hi ho}\"", OsTypeLinux },
{ "echo \"%{echo \"%{a}\"}\"", "echo \"%{echo \"hi\"}\"", OsTypeLinux },
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
const char *title = 0;
for (unsigned i = 0; i < sizeof(vals)/sizeof(vals[0]); i++) {
if (!vals[i].out) {
title = vals[i].in;
} else {
char buf[80];
sprintf(buf, "%s: %s", title, vals[i].in);
QTest::newRow(buf) << QString::fromLatin1(vals[i].in)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< QString::fromLatin1(vals[i].out)
<< vals[i].os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
sprintf(buf, "padded %s: %s", title, vals[i].in);
QTest::newRow(buf) << (sp + QString::fromLatin1(vals[i].in) + sp)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< (sp + QString::fromLatin1(vals[i].out) + sp)
<< vals[i].os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
}
}
void tst_QtcProcess::expandMacros()
{
QFETCH(QString, in);
QFETCH(QString, out);
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QFETCH(OsType, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
if (os == OsTypeWindows)
QtcProcess::expandMacros(&in, &mxWin, os);
else
QtcProcess::expandMacros(&in, &mxUnix, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QCOMPARE(in, out);
}
void tst_QtcProcess::iterations_data()
{
QTest::addColumn<QString>("in");
QTest::addColumn<QString>("out");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QTest::addColumn<OsType>("os");
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
static const struct {
const char * const in;
const char * const out;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
OsType os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
} vals[] = {
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
{ "", "", OsTypeWindows },
{ "hi", "hi", OsTypeWindows },
{ " hi ", "hi", OsTypeWindows },
{ "hi ho", "hi ho", OsTypeWindows },
{ "\"hi ho\" sucker", "\"hi ho\" sucker", OsTypeWindows },
{ "\"hi\"^\"\"ho\" sucker", "\"hi\"\\^\"\"ho\" sucker", OsTypeWindows },
{ "\"hi\"\\^\"\"ho\" sucker", "\"hi\"\\^\"\"ho\" sucker", OsTypeWindows },
{ "hi^|ho", "\"hi|ho\"", OsTypeWindows },
{ "c:\\", "c:\\", OsTypeWindows },
{ "\"c:\\\\\"", "c:\\", OsTypeWindows },
{ "\\hi\\ho", "\\hi\\ho", OsTypeWindows },
{ "hi null%", "hi null%", OsTypeWindows },
{ "hi null% ho", "hi null% ho", OsTypeWindows },
{ "hi null%here ho", "hi null%here ho", OsTypeWindows },
{ "hi null%here%too ho", "hi {} ho", OsTypeWindows },
{ "echo hello | more", "echo hello", OsTypeWindows },
{ "echo hello| more", "echo hello", OsTypeWindows },
{ "", "", OsTypeLinux },
{ " ", "", OsTypeLinux },
{ "hi", "hi", OsTypeLinux },
{ " hi ", "hi", OsTypeLinux },
{ "'hi'", "hi", OsTypeLinux },
{ "hi ho", "hi ho", OsTypeLinux },
{ "\"hi ho\" sucker", "'hi ho' sucker", OsTypeLinux },
{ "\"hi\\\"ho\" sucker", "'hi\"ho' sucker", OsTypeLinux },
{ "\"hi'ho\" sucker", "'hi'\\''ho' sucker", OsTypeLinux },
{ "'hi ho' sucker", "'hi ho' sucker", OsTypeLinux },
{ "\\\\", "'\\'", OsTypeLinux },
{ "'\\'", "'\\'", OsTypeLinux },
{ "hi 'null${here}too' ho", "hi 'null${here}too' ho", OsTypeLinux },
{ "hi null${here}too ho", "hi {} ho", OsTypeLinux },
{ "hi $(echo $dollar cent) ho", "hi {} ho", OsTypeLinux },
{ "hi `echo $dollar \\`echo cent\\` | cat` ho", "hi {} ho", OsTypeLinux },
{ "echo hello | more", "echo hello", OsTypeLinux },
{ "echo hello| more", "echo hello", OsTypeLinux },
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
};
for (unsigned i = 0; i < sizeof(vals)/sizeof(vals[0]); i++)
QTest::newRow(vals[i].in) << QString::fromLatin1(vals[i].in)
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
<< QString::fromLatin1(vals[i].out)
<< vals[i].os;
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
}
void tst_QtcProcess::iterations()
{
QFETCH(QString, in);
QFETCH(QString, out);
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QFETCH(OsType, os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QString outstr;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
for (QtcProcess::ArgIterator ait(&in, os); ait.next(); ) {
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
if (ait.isSimple())
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::addArg(&outstr, ait.value(), os);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
else
QtcProcess::addArgs(&outstr, "{}");
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
}
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QCOMPARE(outstr, out);
}
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
void tst_QtcProcess::iteratorEditsHelper(OsType osType)
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
{
QString in1 = "one two three", in2 = in1, in3 = in1, in4 = in1, in5 = in1;
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::ArgIterator ait1(&in1, osType);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QVERIFY(ait1.next());
ait1.deleteArg();
QVERIFY(ait1.next());
QVERIFY(ait1.next());
QVERIFY(!ait1.next());
QCOMPARE(in1, QString::fromLatin1("two three"));
ait1.appendArg("four");
QCOMPARE(in1, QString::fromLatin1("two three four"));
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::ArgIterator ait2(&in2, osType);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QVERIFY(ait2.next());
QVERIFY(ait2.next());
ait2.deleteArg();
QVERIFY(ait2.next());
ait2.appendArg("four");
QVERIFY(!ait2.next());
QCOMPARE(in2, QString::fromLatin1("one three four"));
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::ArgIterator ait3(&in3, osType);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QVERIFY(ait3.next());
ait3.appendArg("one-b");
QVERIFY(ait3.next());
QVERIFY(ait3.next());
ait3.deleteArg();
QVERIFY(!ait3.next());
QCOMPARE(in3, QString::fromLatin1("one one-b two"));
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::ArgIterator ait4(&in4, osType);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
ait4.appendArg("pre-one");
QVERIFY(ait4.next());
QVERIFY(ait4.next());
QVERIFY(ait4.next());
ait4.deleteArg();
QVERIFY(!ait4.next());
QCOMPARE(in4, QString::fromLatin1("pre-one one two"));
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
QtcProcess::ArgIterator ait5(&in5, osType);
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QVERIFY(ait5.next());
QVERIFY(ait5.next());
QVERIFY(ait5.next());
QVERIFY(!ait5.next());
ait5.deleteArg();
QVERIFY(!ait5.next());
QCOMPARE(in5, QString::fromLatin1("one two"));
}
QtcProcess: Introduce a QtcProcess::Arguments class This is used to get a platform-agnostic handle on "command line arguments". It essentially wraps a single QString on Windows, and a QStringList everywhere else. As a consequence, several occurrences of #ifdef Q_OS_* can be removed from the codebase. Change-Id: Ic93118c1bd0bce0ebb58f416d395dbaebb861772 Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@digia.com>
2014-02-05 10:43:21 +01:00
void tst_QtcProcess::iteratorEditsWindows()
{
iteratorEditsHelper(OsTypeWindows);
}
void tst_QtcProcess::iteratorEditsLinux()
{
iteratorEditsHelper(OsTypeLinux);
}
add Utils::QtcProcess this is a wrapper around QProcess with these features: - setEnvironment() takes a Utils::Environment instead of a QStringList - instead of taking a stringlist with arguments, take a single shell command string which is fully compatible with the system's native shell (the bourne shell on unix and cmd.exe on windows) - with support for environment variable expansion, and subject to the shell's splitting and quoting rules. if the command is too complex (e.g., contains redirections), it is transparently executed through a real shell. - additionally, the class contains a set of helper functions for manipulating (constructing, splitting, etc.) shell command lines. in particular, it contains a shell-safe macro expander and the nested class ArgIterator which can be used for inspecting and manipulating a shell command line without going through the stringlist indirection (which is potentially lossy). some of this is based on KDE code (KShell and KMacroExpander) which i have written myself.
2010-10-14 18:05:43 +02:00
QTEST_MAIN(tst_QtcProcess)
#include "tst_qtcprocess.moc"
Copy Permalink