From: John Smith <witchspace81@gmail•com>
To: Brian McQueen <mcqueenorama@gmail•com>
Cc: Bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Tests for Bitcoin QT
Date: Tue, 4 Oct 2011 17:35:34 +0000 [thread overview]
Message-ID: <CAJNQ0su+UrGLOn+m_mUh6DYDQzOQ6z7KjMWkPGw62d_mPjCiOw@mail.gmail.com> (raw)
In-Reply-To: <CAPfzCrQoP-9aw2SmoFr=FqANBKEJ-zGeOMv08MjtWv-JdXHFDw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]
Hello Brian,
There are no unit tests for the Qt GUI code itself as of this moment.
The tests for the bitcoin core are still there in src/tests >). You need to
build them with the makefile, though. qmake is currently only used for the
GUI executable.
JS
On Mon, Oct 3, 2011 at 11:04 PM, Brian McQueen <mcqueenorama@gmail•com>wrote:
> The Bitcoin QT worked excellently the first time on my Mac. I was so
> surprised to do a pull and compile and bang the new wallet popped up
> and was running. Its much easier than getting it all going from
> makefile and CLI.
>
> However I no longer see the tests subdirectory. How are the unit
> tests handled within this QT framework?
>
> B
> --
> Make a Small Loan, Make a Big Difference - Check out Kiva.org to Learn How!
>
>
> ------------------------------------------------------------------------------
> All the data continuously generated in your IT infrastructure contains a
> definitive record of customers, application performance, security
> threats, fraudulent activity and more. Splunk takes this data and makes
> sense of it. Business sense. IT sense. Common sense.
> http://p.sf.net/sfu/splunk-d2dcopy1
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
[-- Attachment #2: Type: text/html, Size: 1910 bytes --]
prev parent reply other threads:[~2011-10-04 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-03 23:04 Brian McQueen
2011-10-04 17:35 ` John Smith [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJNQ0su+UrGLOn+m_mUh6DYDQzOQ6z7KjMWkPGw62d_mPjCiOw@mail.gmail.com \
--to=witchspace81@gmail$(echo .)com \
--cc=Bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mcqueenorama@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox