Excelon Palindrome: Test Strategy (Connor Roberts)


Get Started. It's Free
or sign up with your email address
Excelon Palindrome: Test Strategy (Connor Roberts) by Mind Map: Excelon Palindrome: Test Strategy (Connor Roberts)

1. Test Techniques

1.1. Functional Testing

1.2. Domain Testing

1.2.1. Data input concerns? Alpha only Alpha-Numeric Special Characters [email protected]#$%^ etc. Spaces UTF-8 compat? (e.g. pictorial language support) Casing Upper Lower Mixed Length Minimum Maximum Numeric only What happens when I submit the same answer multiple times? What if left blank and submitted?

1.3. Stress Testing

1.4. Flow Testing

1.5. Scenario Testing

1.6. Claims Testing

1.7. User Testing

1.8. Risk Testing

1.9. Automatic Checking

1.9.1. Find a list/txt file of existing pailindromes. Use a tool to iterate through them all, auto-refreshing the page and grabbing user message to determine which are/aren't successful.

2. Quality Criteria

2.1. Capability

2.1.1. Data storage Is this all being done client side, or are we storing answers in a DB/file on the server? Are we using cookies? caching? etc. Does refreshing the page lose currently input data or is that preserved?

2.2. Reliability

2.3. Usability

2.3.1. UX What visual notifications/responses are given to the user? When a palindrome is entered? When a non-palindrome is entered? After answer entry, does the form reset or does the user have to reset it? Can I type in the field? As I type, am I supposed to get any kind of live feedback? (autocomplete, form validation, etc.) Should the submit button be disabled until I type in the minimum characters?

2.4. Charisma

2.5. Security

2.5.1. Security What kind of transmission is used between the form and the server? Does this need to be secure? SSL/HTTPS? Certificates?

2.6. Scalability

2.6.1. What other functions/abilities does this Palindrome feature need to do in the future? How easy will it be for those teams/devs to add on to it?

2.7. Compatibility

2.7.1. What other products need to digest data output by this program?

2.7.2. External Multi-Browser Mobile, Tablet, etc. Desktop

2.8. Performance

2.8.1. Timing Submit typical response at 11:59:00 Submit typical response at 12:00:00 Submit typical response at 23:59:59 Submit typical response at 00:00:00

2.8.2. How many asserts does the site need to serve at once (1/min, 1000/s, etc)?

2.9. Installability

2.10. Development

2.10.1. Analytics What data do we have on current usage? i.e. trends to drive the establishment of User Personas to better guide future testing For example, if 80% of our users are consistently only ever putting in alpha-numeric characters only, then maybe the large portion of our testing should focus on that. What bugs have been found/reported recently by other groups?

2.10.2. Code Use RCRCRC model to address regression concerns (what areas of the code have been modified in these areas that we need to be concerned with) Recent Core Risky Chronic Repaired Configuration What language is this written in? Any known risks/limitations using this lang to write past similar functions? Look at the page source code to see if there are any obvious logic flaws or scenarios that would immediately fail (this snippet may include more than just the palindrome code) //Authors:        // Paul Harju ([email protected])        // Justin Rohrman        function isPalindrome() {        var original        original = document.getElementById("originalWord").value;        var palindrome = original.split("").reverse().join("");        if ( original === palindrome) {            document.getElementById("palindromeResult").innerHTML = "Yes! " + original + " reversed is " + palindrome;        }        else {            document.getElementById("palindromeResult").innerHTML = "No! " + original + " reserved is " + palindrome;        }                }        function shuffle(o){ //v1.0            for(var j, x, i = o.length; i; j = Math.floor(Math.random() * i), x = o[--i], o[i] = o[j], o[j] = x);            return o;        };        function makeAnagram() {            var original            original = document.getElementById("anagramWord").value;                        var anagramList = "";            document.getElementById("anagramResult").innerHTML = "5 potential anagrams:</br>";                        for (var i = 0;  i < 5; i++) {                var anagram = shuffle(original.split("")).join("");                document.getElementById("anagramResult").innerHTML += anagram + "</br>";            }        }

3. Testing Priorities

3.1. High (large amount of testing effort)

3.2. Medium (moderate amount of testing effort)

3.3. Low (little to no testing effort)

4. Product Elements

4.1. Structure

4.2. Function

4.3. Data

4.4. Interfaces

4.5. Platform

4.6. Operations

4.7. Time

5. Consistency

5.1. Familiarity

5.2. Explainability

5.3. World

5.4. History

5.5. Image

5.6. Comparable Products

5.7. Claims

5.8. Users’ Desires

5.9. Product

5.10. Purpose

5.11. Statutes and Standards

6. Other Questions/Concerns

6.1. External Resources

6.1.1. Do we have access to the development team that last worked on this/originally made it?