pcgen-trackers_project_test_requests — This mailing list will send out every Project Test Request related trackers

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-47) Add VFEAT granting to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11287#action_11287 ] 

Tom Parker commented on TEST-47:
--------------------------------

Targets absolutely can have sub items in parenthesis.  See this example:

ParentThingyType1 <> VFEAT:GivingThingy(NoChooseFeat)
ParentThingyType2 <> VFEAT:GivingThingy(NoStackNoChoiceFeat)
ParentThingyType3 <> VFEAT:GivingThingy(NoStackChoiceFeat(Ride))
ParentThingyType4 <> VFEAT:GivingThingy(StackNoChoiceFeat)
ParentThingyType5 <> VFEAT:GivingThingy(StackChoiceFeat(Ride))|GivingThingy(StackChoiceFeat(Tumble))
ParentThingyType6 <> VFEAT:GivingThingy(StackNoChoiceFeat)
ParentThingyType7 <> VFEAT:GivingThingy(StackChoiceFeat(Ride))|GivingThingy(StackChoiceFeat(Ride))|GivingThingy(StackChoiceFeat(Tumble))
GivingThingy <> CHOOSE:FEATSELECTION <> MULT:YES <> STACK:YES <> AUTO:FEAT|%LIST
NoChooseFeat
NoStackFeat <> CHOOSE:NOCHOICE <> MULT:YES
NoStackChoiceFeat <> CHOOSE:SKILL|ANY <> MULT:YES
StackNoChoiceFeat <> CHOOSE:NOCHOICE <> MULT:YES <> STACK:YES
StackChoiceFeat <> CHOOSE:SKILL|ANY <> MULT:YES <> STACK:YES

The other similar test requests follow a similar pattern.  all that is changing is VFEAT vs. other tokens.



> Add VFEAT granting to Character Tests
> -------------------------------------
>
>                 Key: TEST-47
>                 URL: http://jira.pcgen.org/browse/TEST-47
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> 1) Ability granted by a VFEAT token where the target (in parens) is MULT:NO
> 2) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
> 3) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
> 4) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
> 5) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
> 6) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
> 7) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)
> Example is:
> VFEAT:SomeAbility(SuperDuperLaserAbility)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-48) Add AUTO:FEAT Granting to Character Tests

[Andrew M. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-48?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11284#action_11284 ] 

Andrew Maitland commented on TEST-48:
-------------------------------------

See comments in TEST-46 and TEST-47. Test cannot be objectively completed as requested without clarification of intent.

> Add AUTO:FEAT Granting to Character Tests
> -----------------------------------------
>
>                 Key: TEST-48
>                 URL: http://jira.pcgen.org/browse/TEST-48
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> 1) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:NO
> 2) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
> 3) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
> 4) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
> 5) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
> 6) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
> 7) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)
> Example is:
> AUTO:FEAT|SomeAbility(SuperDuperLaserAbility) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-47) Add VFEAT granting to Character Tests

[Andrew M. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-47?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11283#action_11283 ] 

Andrew Maitland commented on TEST-47:
-------------------------------------

These tests are non-completable as requested - no target in a parens ever has "MULT", "STACK" or even "CHOOSE", the Target is the End Result of the Originating Object. The Originating Object has those Attributes. I think that's what you are requesting, but I need clarification - here are some examples:

Skill Focus(Spellcraft)  -- Spellcraft is the Target, Skill Focus is the Originating Object. 
Dodge(Spellcraft) -- would be an interesting nonsensical result - as Dodge has no Target Capability. 

Please Clarify Request to something I can actually achieve.

> Add VFEAT granting to Character Tests
> -------------------------------------
>
>                 Key: TEST-47
>                 URL: http://jira.pcgen.org/browse/TEST-47
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> 1) Ability granted by a VFEAT token where the target (in parens) is MULT:NO
> 2) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
> 3) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
> 4) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
> 5) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
> 6) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
> 7) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)
> Example is:
> VFEAT:SomeAbility(SuperDuperLaserAbility)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-46) Add Conditional Abilities with Targets to Character Tests

[Andrew M. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-46?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11282#action_11282 ] 

Andrew Maitland commented on TEST-46:
-------------------------------------

These tests are non-completable as requested - no target in a parens ever has "MULT", "STACK" or even "CHOOSE", the Target is the End Result of the Originating Object. The Originating Object has those Attributes. I think that's what you are requesting, but I need clarification - here are some examples:

Skill Focus(Spellcraft)  -- Spellcraft is the Target, Skill Focus is the Originating Object. 
Dodge(Spellcraft) -- would be an interesting nonsensical result - as Dodge has no Target Capability. 

Please Clarify Request to something I can actually achieve.

> Add Conditional Abilities with Targets to Character Tests
> ---------------------------------------------------------
>
>                 Key: TEST-46
>                 URL: http://jira.pcgen.org/browse/TEST-46
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> Request 7 instances of CHOOSE:FEATSELECTION used in the test PCs (Alice, Bob, Charlie)
> 1) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:NO
> 2) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
> 3) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
> 4) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
> 5) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
> 6) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
> 7) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)
> Example is:
> ABILITY:FEAT|AUTOMATIC|SomeAbility(SuperDuperLaserAbility)|PRELEVEL:2
> SuperDuperLaserAbility is the target.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-50) Test AUTO:EQUIP|%LIST

[Tom P. (JIRA) <ji...@pc...>]

Test AUTO:EQUIP|%LIST
---------------------

                 Key: TEST-50
                 URL: http://jira.pcgen.org/browse/TEST-50
             Project: Project Test Requests
          Issue Type: Task
            Reporter: Tom Parker


It is possible that AUTO:EQUIP|%LIST 
on a CHOOSE:EQUIPMENT Ability will provide the equipment more than one time to a PC.
Please test.  Level the character up afterwords, and do a few other changes, ensuring that only 1 copy of the equipment appears.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-49) Add Unconditional Abilities to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

Add Unconditional Abilities to Character Tests
----------------------------------------------

                 Key: TEST-49
                 URL: http://jira.pcgen.org/browse/TEST-49
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


Request 7 instances of CHOOSE:FEATSELECTION used in the test PCs (Alice, Bob, Charlie)

1) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:NO
2) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
3) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
4) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
5) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
6) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
7) Ability granted by a deferred unconditional ABILITY token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)


Example is:
ABILITY:FEAT|AUTOMATIC|SomeAbility(SuperDuperLaserAbility)

SuperDuperLaserAbility is the target.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-48) Add AUTO:FEAT Granting to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

Add AUTO:FEAT Granting to Character Tests
-----------------------------------------

                 Key: TEST-48
                 URL: http://jira.pcgen.org/browse/TEST-48
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


1) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:NO
2) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
3) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
4) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
5) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
6) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
7) Ability granted by a AUTO:FEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)


Example is:
AUTO:FEAT|SomeAbility(SuperDuperLaserAbility) 

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-47) Add VFEAT granting to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

Add VFEAT granting to Character Tests
-------------------------------------

                 Key: TEST-47
                 URL: http://jira.pcgen.org/browse/TEST-47
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


1) Ability granted by a VFEAT token where the target (in parens) is MULT:NO
2) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
3) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
4) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
5) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
6) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
7) Ability granted by a VFEAT token where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)


Example is:
VFEAT:SomeAbility(SuperDuperLaserAbility)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-46) Add Conditional Abilities with Targets to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

Add Conditional Abilities with Targets to Character Tests
---------------------------------------------------------

                 Key: TEST-46
                 URL: http://jira.pcgen.org/browse/TEST-46
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


Request 7 instances of CHOOSE:FEATSELECTION used in the test PCs (Alice, Bob, Charlie)

1) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:NO
2) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:NO CHOOSE:NOCHOICE
3) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
4) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
5) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
6) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
7) Ability granted by a deferred conditional ABILITY token (e.g. PRELEVEL:2 but attached to class level 1) where the target (in parens) is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)


Example is:
ABILITY:FEAT|AUTOMATIC|SomeAbility(SuperDuperLaserAbility)|PRELEVEL:2

SuperDuperLaserAbility is the target.



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-45) Add CHOOSE:FEATSELECTION to Character Tests

[Tom P. (JIRA) <ji...@pc...>]

Add CHOOSE:FEATSELECTION to Character Tests
-------------------------------------------

                 Key: TEST-45
                 URL: http://jira.pcgen.org/browse/TEST-45
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


Request 7 instances of CHOOSE:FEATSELECTION used in the test PCs (Alice, Bob, Charlie)

1) CHOOSE:FEATSELECTION where the target is MULT:NO
2) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:NO CHOOSE:NOCHOICE
3) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:NO and any CHOOSE except NOCHOICE or USERINPUT.
4) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are only chosen once (STACK is effectively left unused)
5) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are only chosen once (STACK is effectively left unused)
6) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:YES CHOOSE:NOCHOICE and the stackable items are chosen more than once (STACK is used)
7) CHOOSE:FEATSELECTION where the target is MULT:YES STACK:YES and any CHOOSE except NOCHOICE or USERINPUT. and the stackable items are chosen more than once (STACK is used)


The target (obviously) is the item selected in the chooser window, not the item that contains the CHOOSE:FEATSELECTION



-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-43) Test Template LST FEAT token application to a PC

[Andrew M. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11113#action_11113 ] 

Andrew Maitland commented on TEST-43:
-------------------------------------

The Syntax was wrong, once I corrected that, all the tests fail. I verified that the feat itself works.

> Test Template LST FEAT token application to a PC
> ------------------------------------------------
>
>                 Key: TEST-43
>                 URL: http://jira.pcgen.org/browse/TEST-43
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>
> NOTE: ALL Feats applied by FEAT: in this example MUST have a selection.  In other words, they MUST be MULT:YES with a CHOOSE: token present.  Not CHOOSE:NOCHOICE.... because:  They also must USE the result of the CHOOSE (using %LIST) in an AUTO: token.
> The above NOTE is required to produce the desired test, e.g.
> Feat One ("Weapon Foo"):
> AUTO:WEAPONPROF|%LIST
> CHOOSE:WEAPONPROF|ALL 
> (I think you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo, if that exists in, or is easily added to, the test set)
> 3 instances of FEAT: used in a Template are part of this test request:
> (1) base FEAT:, e.g.:
> FEAT:Weapon Foo(Longsword)
> (2) LEVEL with FEAT, e.g.:
> LEVEL:2:FEAT:Weapon Foo(Dagger)
> (3) HD with FEAT, e.g.:
> HD:2:FEAT:Weapon Foo(Staff)
> p.s. Just like the last one, this may break.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Assigned: (TEST-43) Test Template LST FEAT token application to a PC

[Andrew M. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-43?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Maitland reassigned TEST-43:
-----------------------------------

    Assignee: Andrew Maitland

> Test Template LST FEAT token application to a PC
> ------------------------------------------------
>
>                 Key: TEST-43
>                 URL: http://jira.pcgen.org/browse/TEST-43
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>
> NOTE: ALL Feats applied by FEAT: in this example MUST have a selection.  In other words, they MUST be MULT:YES with a CHOOSE: token present.  Not CHOOSE:NOCHOICE.... because:  They also must USE the result of the CHOOSE (using %LIST) in an AUTO: token.
> The above NOTE is required to produce the desired test, e.g.
> Feat One ("Weapon Foo"):
> AUTO:WEAPONPROF|%LIST
> CHOOSE:WEAPONPROF|ALL 
> (I think you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo, if that exists in, or is easily added to, the test set)
> 3 instances of FEAT: used in a Template are part of this test request:
> (1) base FEAT:, e.g.:
> FEAT:Weapon Foo(Longsword)
> (2) LEVEL with FEAT, e.g.:
> LEVEL:2:FEAT:Weapon Foo(Dagger)
> (3) HD with FEAT, e.g.:
> HD:2:FEAT:Weapon Foo(Staff)
> p.s. Just like the last one, this may break.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-42) Test Conditional Selected Ability Application

[Andrew M. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11094#action_11094 ] 

Andrew Maitland commented on TEST-42:
-------------------------------------

First Test - Passes

Second Test FAILS -

Item Test 42 2	TYPE:Goods		ABILITY:FEAT|VIRTUAL|Weapon Focus(Longsword)|PRELEVEL:MAX=4

Weapon Focus(Longsword) remains applied at 5th level.

> Test Conditional Selected Ability Application
> ---------------------------------------------
>
>                 Key: TEST-42
>                 URL: http://jira.pcgen.org/browse/TEST-42
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>
> Background:
> An Item of the form:
> ABILITY:CATEGORY|NATURE|Feat (Selection)|PRExxx:y
> may not apply properly.
> Required to produce the test (you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo shown below, if that exists in, or is easily added to, the test set)
> Feat One ("Weapon Foo"):
> AUTO:WEAPONPROF|%LIST
> CHOOSE:WEAPONPROF|ALL
> Two separate tests are requested. 
> Test #1, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3]):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MIN=4
> Test #2, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3)):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MAX=4
> In both cases, the PC should be a minimum of level 5.
> You may change the levels PROVIDED that the token above (the ABILITY token) is ALWAYS possessed by the PC prior to the level of the PC.  e.g. if they are applied at level 1 (via template, another ability, PCClass, whatever) and the PRELEVEL is =2 and the PC is level 3, that's OK.
> The two tests MUST test separate proficiencies (or be applied to different test PCs) in order to properly distinguish behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Assigned: (TEST-42) Test Conditional Selected Ability Application

[Andrew M. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Maitland reassigned TEST-42:
-----------------------------------

    Assignee: Andrew Maitland

> Test Conditional Selected Ability Application
> ---------------------------------------------
>
>                 Key: TEST-42
>                 URL: http://jira.pcgen.org/browse/TEST-42
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>
> Background:
> An Item of the form:
> ABILITY:CATEGORY|NATURE|Feat (Selection)|PRExxx:y
> may not apply properly.
> Required to produce the test (you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo shown below, if that exists in, or is easily added to, the test set)
> Feat One ("Weapon Foo"):
> AUTO:WEAPONPROF|%LIST
> CHOOSE:WEAPONPROF|ALL
> Two separate tests are requested. 
> Test #1, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3]):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MIN=4
> Test #2, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3)):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MAX=4
> In both cases, the PC should be a minimum of level 5.
> You may change the levels PROVIDED that the token above (the ABILITY token) is ALWAYS possessed by the PC prior to the level of the PC.  e.g. if they are applied at level 1 (via template, another ability, PCClass, whatever) and the PRELEVEL is =2 and the PC is level 3, that's OK.
> The two tests MUST test separate proficiencies (or be applied to different test PCs) in order to properly distinguish behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Updated: (TEST-44) Enhance TEST-43 result to add conditional application of Templates

[Tom P. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-44?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker updated TEST-44:
---------------------------

    Description: 
The 3 templates from TEST-43 should now be applied to/removed from a PC based on conditions, e.g.:
Ability "Application Test A"
TEMPLATE:Test-43-A

Ability "Application Test B"
TEMPLATE:Test-43-B

Ability "Application Test C"
TEMPLATE:Test-43-C

then elsewhere for the PC:
ABILITY:FEAT|VIRTUAL|Application Test A|PRELEVEL:MAX=2
ABILITY:FEAT|VIRTUAL|Application Test B|PRELEVEL:MAX=3
ABILITY:FEAT|VIRTUAL|Application Test C|PRELEVEL:MAX=4

Note like TEST-42, altering the MAX levels is OK as long as the items containing the ABILITY tokens shown above are applied before the level in the PRExxx is reached, and the PC is higher than all of the shown levels (items in this example would be applied at level 1, and PC would be a minimum o level 5)


  was:
The 3 templates from TEST-43 should now be applied to/removed from a PC based on conditions, e.g.:
Ability "Application Test A"
TEMPLATE:Test-43-A

Ability "Application Test B"
TEMPLATE:Test-43-B

Ability "Application Test C"
TEMPLATE:Test-43-C

then elsewhere for the PC:
ABILITY:FEAT|VIRTUAL|Application Test A|PRELEVEL:MAX=2
ABILITY:FEAT|VIRTUAL|Application Test B|PRELEVEL:MAX=3
ABILITY:FEAT|VIRTUAL|Application Test C|PRELEVEL:MAX=4

Note like TEST-41, altering the MAX levels is OK as long as the items containing the ABILITY tokens shown above are applied before the level in the PRExxx is reached, and the PC is higher than all of the shown levels (items in this example would be applied at level 1, and PC would be a minimum o level 5)



> Enhance TEST-43 result to add conditional application of Templates
> ------------------------------------------------------------------
>
>                 Key: TEST-44
>                 URL: http://jira.pcgen.org/browse/TEST-44
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> The 3 templates from TEST-43 should now be applied to/removed from a PC based on conditions, e.g.:
> Ability "Application Test A"
> TEMPLATE:Test-43-A
> Ability "Application Test B"
> TEMPLATE:Test-43-B
> Ability "Application Test C"
> TEMPLATE:Test-43-C
> then elsewhere for the PC:
> ABILITY:FEAT|VIRTUAL|Application Test A|PRELEVEL:MAX=2
> ABILITY:FEAT|VIRTUAL|Application Test B|PRELEVEL:MAX=3
> ABILITY:FEAT|VIRTUAL|Application Test C|PRELEVEL:MAX=4
> Note like TEST-42, altering the MAX levels is OK as long as the items containing the ABILITY tokens shown above are applied before the level in the PRExxx is reached, and the PC is higher than all of the shown levels (items in this example would be applied at level 1, and PC would be a minimum o level 5)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-44) Enhance TEST-43 result to add conditional application of Templates

[Tom P. (JIRA) <ji...@pc...>]

Enhance TEST-43 result to add conditional application of Templates
------------------------------------------------------------------

                 Key: TEST-44
                 URL: http://jira.pcgen.org/browse/TEST-44
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


The 3 templates from TEST-43 should now be applied to/removed from a PC based on conditions, e.g.:
Ability "Application Test A"
TEMPLATE:Test-43-A

Ability "Application Test B"
TEMPLATE:Test-43-B

Ability "Application Test C"
TEMPLATE:Test-43-C

then elsewhere for the PC:
ABILITY:FEAT|VIRTUAL|Application Test A|PRELEVEL:MAX=2
ABILITY:FEAT|VIRTUAL|Application Test B|PRELEVEL:MAX=3
ABILITY:FEAT|VIRTUAL|Application Test C|PRELEVEL:MAX=4

Note like TEST-41, altering the MAX levels is OK as long as the items containing the ABILITY tokens shown above are applied before the level in the PRExxx is reached, and the PC is higher than all of the shown levels (items in this example would be applied at level 1, and PC would be a minimum o level 5)


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-43) Test Template LST FEAT token application to a PC

[Tom P. (JIRA) <ji...@pc...>]

Test Template LST FEAT token application to a PC
------------------------------------------------

                 Key: TEST-43
                 URL: http://jira.pcgen.org/browse/TEST-43
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


NOTE: ALL Feats applied by FEAT: in this example MUST have a selection.  In other words, they MUST be MULT:YES with a CHOOSE: token present.  Not CHOOSE:NOCHOICE.... because:  They also must USE the result of the CHOOSE (using %LIST) in an AUTO: token.

The above NOTE is required to produce the desired test, e.g.
Feat One ("Weapon Foo"):
AUTO:WEAPONPROF|%LIST
CHOOSE:WEAPONPROF|ALL 
(I think you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo, if that exists in, or is easily added to, the test set)

3 instances of FEAT: used in a Template are part of this test request:
(1) base FEAT:, e.g.:
FEAT:Weapon Foo(Longsword)
(2) LEVEL with FEAT, e.g.:
LEVEL:2:FEAT:Weapon Foo(Dagger)
(3) HD with FEAT, e.g.:
HD:2:FEAT:Weapon Foo(Staff)

p.s. Just like the last one, this may break.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Commented: (TEST-42) Test Conditional Selected Ability Application

[Tom P. (JIRA) <ji...@pc...>]

    [ http://jira.pcgen.org/browse/TEST-42?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11093#action_11093 ] 

Tom Parker commented on TEST-42:
--------------------------------

p.s. I expect this to expose a bug, so this may not be able to be checked in immediately, and don't be surprised if it doesn't seem to work.  Most likely it will not unapply the item when the PRExxx is no longer valid. (Test #2 will not unapply the weapon proficiency)

p.p.s.  If you use Martial Weapon Proficiency, make sure the PC doesn't have the proficiency automatically, as that will skew the results of the test (obviously :) )


> Test Conditional Selected Ability Application
> ---------------------------------------------
>
>                 Key: TEST-42
>                 URL: http://jira.pcgen.org/browse/TEST-42
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>
> Background:
> An Item of the form:
> ABILITY:CATEGORY|NATURE|Feat (Selection)|PRExxx:y
> may not apply properly.
> Required to produce the test (you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo shown below, if that exists in, or is easily added to, the test set)
> Feat One ("Weapon Foo"):
> AUTO:WEAPONPROF|%LIST
> CHOOSE:WEAPONPROF|ALL
> Two separate tests are requested. 
> Test #1, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3]):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MIN=4
> Test #2, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3)):
> ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MAX=4
> In both cases, the PC should be a minimum of level 5.
> You may change the levels PROVIDED that the token above (the ABILITY token) is ALWAYS possessed by the PC prior to the level of the PC.  e.g. if they are applied at level 1 (via template, another ability, PCClass, whatever) and the PRELEVEL is =2 and the PC is level 3, that's OK.
> The two tests MUST test separate proficiencies (or be applied to different test PCs) in order to properly distinguish behavior.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-42) Test Conditional Selected Ability Application

[Tom P. (JIRA) <ji...@pc...>]

Test Conditional Selected Ability Application
---------------------------------------------

                 Key: TEST-42
                 URL: http://jira.pcgen.org/browse/TEST-42
             Project: Project Test Requests
          Issue Type: Code/Data Integration Test Request
            Reporter: Tom Parker


Background:
An Item of the form:
ABILITY:CATEGORY|NATURE|Feat (Selection)|PRExxx:y
may not apply properly.

Required to produce the test (you can use "Martial Weapon Proficiency" from an SRD instead of Weapon Foo shown below, if that exists in, or is easily added to, the test set)
Feat One ("Weapon Foo"):
AUTO:WEAPONPROF|%LIST
CHOOSE:WEAPONPROF|ALL

Two separate tests are requested. 

Test #1, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3]):
ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MIN=4

Test #2, please apply the following to an item possessed by the PC (prior to level 4 [meaning <=3)):
ABILITY:FEAT|VIRTUAL|Weapon Foo(Longsword)|PRELEVEL:MAX=4

In both cases, the PC should be a minimum of level 5.

You may change the levels PROVIDED that the token above (the ABILITY token) is ALWAYS possessed by the PC prior to the level of the PC.  e.g. if they are applied at level 1 (via template, another ability, PCClass, whatever) and the PRELEVEL is =2 and the PC is level 3, that's OK.

The two tests MUST test separate proficiencies (or be applied to different test PCs) in order to properly distinguish behavior.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Created: (TEST-41) ** REQ vs. PRE Behaviors

[Andrew M. (JIRA) <ji...@pc...>]

** REQ vs. PRE Behaviors
------------------------

                 Key: TEST-41
                 URL: http://jira.pcgen.org/browse/TEST-41
             Project: Project Test Requests
          Issue Type: Task
         Environment: Trunk
            Reporter: Andrew Maitland


TO assist Code in breaking out REQ and PRE behaviors.

****
REQ Pool: the following with grant or remove based upon meeting the Requirements

VFEAT
DESC
BENEFIT
ABILITY
BONUS

PRE POOL: the following will be granted upon meeting the prereqs.

PRExxx as a standalone inside an ability/feat/template that can be manually taken. Once taken the item remains attached.

Ability 
Feat
Template
Skill - *If Prereq no longer met, UI will not allow the skill to add or remove skill ranks.

Noted Behaviors -

ADD will respect any Ability that has an internal PRE tag, and will allow or disallow the taking of the object at the current time of firing, once added, the object will remain regardless if the prereq is met afterwards.

Granting Objects with an Attached PRE all act as REQ


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Closed: (TEST-23) Skill Cost testing (Class Skills)

[Andrew M. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-23?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Andrew Maitland closed TEST-23.
-------------------------------

      Assignee: Andrew Maitland
    Resolution: Test Passes

All test passes.

> Skill Cost testing (Class Skills)
> ---------------------------------
>
>                 Key: TEST-23
>                 URL: http://jira.pcgen.org/browse/TEST-23
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>            Priority: Major
>
> Need to have 9 methods of adding Class Skills to a Player Character in our test data (ABC)
> CSKILL in an Ability
> CSKILL in a Domain
> CSKILL in a PCClass (on the CLASS: line)
> CSKILL in a Class Level (on a class level line - please do not use level 1)
> ADD:CLASSSKILLS on a CLASS: line
> ADD:CLASSSKILLS on a class level line (please do not use level 1)
> CSKILL:LIST in a Domain
> CSKILL:LIST in an Ability
> CLASSES in the Skill LST file

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Closed: (TEST-31) Movement Testing

[Tom P. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker closed TEST-31.
--------------------------


Note I think this is weird that Crawl shows up as 35, but the code clearly intends to do it... need to think about this in movement rebuild


> Movement Testing
> ----------------
>
>                 Key: TEST-31
>                 URL: http://jira.pcgen.org/browse/TEST-31
>             Project: Project Test Requests
>          Issue Type: Code/Data Integration Test Request
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>            Priority: Major
>
> Have the following in a PC:
> MOVECLONE using a + with a new movement type (e.g. Trot)
> BONUS:MOVEADD|TYPE.Crawl|x (MUST be a movement type the PC doesn't already have) (need to pick X)
>    (this type of movement should be added)
> BONUS:MOVEMULT|TYPE.Shuffle|y (MUST be a movement type the PC doesn't already have)
>    (this type of movement should NOT be added)
> BONUS:POSTMOVEADD|TYPE.Scramble|y (MUST be a movement type the PC doesn't already have)
>    (this type of movement should NOT be added)
>  
> Have the following in a second PC:
> MOVECLONE using a * with a new movement type (e.g. Fly)
> BONUS:MOVEADD|TYPE.ALL|x  (need to pick X)
>    (should impact all types of movement, but NOT add an "ALL" movement type)
> BONUS:MOVEMULT|TYPE.ALL|x  (need to pick X)
> BONUS:POSTMOVEADD|TYPE.ALL|x  (need to pick X)
> Have the following in a third PC:
> MOVECLONE using a / with a new movement type (e.g. Swim)
> BONUS:MOVEADD|TYPE.Swim|x  (need to pick X)
> BONUS:MOVEMULT|TYPE.Swim|x  (need to pick X)
> BONUS:POSTMOVEADD|TYPE.Swim|x  (need to pick X)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Reopened: (TEST-24) Test LEVEL:2:ADD:FEAT|Foo in Template LST

[Tom P. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-24?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker reopened TEST-24:
----------------------------


reopened, pending code fix for further work


> Test LEVEL:2:ADD:FEAT|Foo in Template LST
> -----------------------------------------
>
>                 Key: TEST-24
>                 URL: http://jira.pcgen.org/browse/TEST-24
>             Project: Project Test Requests
>          Issue Type: Task
>            Reporter: Tom Parker
>            Assignee: Andrew Maitland
>
> Please test LEVEL:2:ADD:FEAT|Foo (you will need to test with a real Feat)
> I believe this will fail to fire the ADD chooser, and if so, should be a bug.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Closed: (TEST-9) Test Fractional Movement Multipliers

[Tom P. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-9?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker closed TEST-9.
-------------------------


This issue was to validate the FREQ was needed (it is)


> Test Fractional Movement Multipliers
> ------------------------------------
>
>                 Key: TEST-9
>                 URL: http://jira.pcgen.org/browse/TEST-9
>             Project: Project Test Requests
>          Issue Type: Task
>            Reporter: Tom Parker
>            Assignee: Tom Parker
>
> See SourceForge tracker 1623870
> I believe this is possible with a combination of BONUS:MOVEMULT and/or MOVECLONE.  Please verify both support formulas (including #s 0<x<1)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[Pcgen-trackers_project_test_requests] [JIRA] Reopened: (TEST-25) Test TEMPLATE LST FEAT token with different conditions

[Tom P. (JIRA) <ji...@pc...>]

     [ http://jira.pcgen.org/browse/TEST-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tom Parker reopened TEST-25:
----------------------------

      Assignee:     (was: Tom Parker)

> Test TEMPLATE LST FEAT token with different conditions
> ------------------------------------------------------
>
>                 Key: TEST-25
>                 URL: http://jira.pcgen.org/browse/TEST-25
>             Project: Project Test Requests
>          Issue Type: Task
>            Reporter: Tom Parker
>
> Test A)
> FEAT:Agile
> I believe this should properly apply to the PC and the PC will be charged a point from the Feat Pool
> Test B)
> FEAT:Toughness
> I believe this should properly apply to the PC and the PC will be NOT charged a point from the Feat Pool
> Test C)
> FEAT:Weapon Focus(Longsword)
> I believe this should properly apply to the PC and the PC will be NOT charged a point from the Feat Pool

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.pcgen.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira