However this has led me to a problem - obviously to test the basic functionality (e.g. getting my account balance) I need to put in my secure banking details
You're doing end-to-end testing and unit testing at the same time it sounds.
Don't do that. Distribute your unit tests. They show patterns of use of the API you are writing.
Keep your end-to-end tests closest to your QA group (yourself likely). They are more brittle, unlike unit tests. Unit tests are small, discrete. end-to-end layers your unit tests in ways that can break when integrated, lack a perfect environment or are configured in odd ways.
Persons w/ a large POV will value them more because they are more likely to find edge case bugs.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
