search

SME-Issues / issues

0 stars 0 forks source link

Followup Tests Non Canonical - 04/07/19 09:25 - 5004 #4789

Open SME-Issues opened 5 years ago

SME-Issues commented 5 years ago

Followup Tests Non Canonical

SME-Issues commented 5 years ago

Understood and failed but likely higher priority

Expressions Notes
could I get a look at May while we're doing this
After pre-processingcould I get a look at May while we are doing this
  • expected original intent set_date but found only query_payment
  • Response: I've just queried for you and in May 2019 your expenditure was nine payments totalling £4,792.
if that was the case then which were overdue
  • Expected a single BankingContext but found two
  • Other than 'extras, confirmations & unknown/none' expected a single chunk but found 2
  • Response: I've just checked the up-to-the-minute situation and the amount owed to creditors is nine unpaid bills totalling £4,841 of which seven are overdue. The amount owed from debtors is nine unpaid invoices totalling £9,857 of which four are overdue. The overdue amount owed to creditors is seven bills totalling £4,490. The overdue amount owed from debtors is four invoices totalling £1,714.
SME-Issues commented 5 years ago

Understood and failed but likely lower priority

Expressions Notes
and which of those finally got paid
  • Expected to find entity 'closed_mod' but found only {dt, text, date_in, date_mod, datetime}
  • Response: I've just checked the up-to-the-minute situation and since 5th June 2019 your spending was nine payments totalling £3,316.
and which of those got paid
  • Expected to find entity 'closed_mod' but found only {dt, text, date_in, date_mod, datetime}
  • Response: After checking, I can verify that since 5th June 2019 your expenditure was nine payments totalling £3,316.
did they get paid
  • Expected to find entity 'closed_mod' but found only {paid_yet, prior_pronoun, pay_to, text, date_in, date_mod, datetime}
  • Response: After checking, I can verify that since 5th June 2019 your outgoings were nine payments totalling £3,316.
did we pay them
  • Expected to find entity 'prior_pronoun' but found only {paid_yet, pay_to, text, date_in, date_mod, datetime}
  • Response: I've performed a quick investigation and since 5th June 2019 your outgoings were nine payments totalling £3,316.
show me the ones that got paid
  • Expected to find entity 'closed_mod' but found only {paid_query, text, date_in, date_mod, datetime}
  • Response: I've gone through the most recent figures and since 5th June 2019 your outgoings were nine payments totalling £3,316.
tell me which were paid
  • Expected to find entity 'closed_mod' but found only {paid_query, date_in, date_mod, datetime}
  • Response: I've just queried for you and since 5th June 2019 your spending was nine payments totalling £3,316.
were any of them paid
  • Expected to find entity 'prior_pronoun' but found only {paid_query, closed_mod, dt, text, date_in, date_mod, datetime}
  • Response: I've checked that out and since 5th June 2019 your spending was nine payments totalling £3,316.
which one came through last
  • Other than 'extras, confirmations & unknown/none' expected a single chunk but found 2
  • Response: Regrettably, I didn't recognise everything you said, however your latest outgoing payment was to ABC Ltd and was for £190. It was paid on the 29th June 2019.
how does January appear in comparison
  • expected original intent set_date but found only query_balance
  • Expected to find entity 'datetime' but found only {unknown_entity, wrb, vbz, date, amount, text}
  • Response: I didn't understand all of that, however you have £2,082 in your current account and £22,380 in your savings account.
if that's the case, better see the july ones too
After pre-processingif that is the case, better see the july ones too
  • expected original intent set_date but found only query_invoices, unknown
  • Response: Regrettably, I didn't recognise everything you said, however in July 2019 you received two invoices totalling £350, neither of which have been paid and you raised five invoices totalling £8,143, none of which have been paid.
are any of those especially big
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: Regrettably, I didn't recognise everything you said, however since 5th June 2019 your expenditure was nine payments totalling £3,316.
are any of those exceptionally big
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: Regrettably, I didn't recognise everything you said, however since 5th June 2019 your expenditure was nine payments totalling £3,316.
are any of those particularly big
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: I didn't understand all of that, however since 5th June 2019 your spending was nine payments totalling £3,316.
pass me the most sizeable one
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: I'm sorry but I didn't understand all of that, however since 5th June 2019 your outgoings were nine payments totalling £3,316.
show me the one of greater size
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected to find entity 'comparator' but found only {unknown_entity, text, date_in, date_mod, datetime}
  • Response: Hang on - I didn't quite understand all that, however since 5th June 2019 your spending was nine payments totalling £3,316.
which of those is the most considerably sizable
After pre-processingwhich of those is the most considerably sizeable
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: I'm afraid I didn't quite get all of that, however since 5th June 2019 your spending was nine payments totalling £3,316.
which of those is the most markedly sizable
After pre-processingwhich of those is the most markedly sizeable
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected {comparator} to have single value 'biggest' but found 'big'
  • Response: Regrettably, I didn't recognise everything you said, however since 5th June 2019 your spending was nine payments totalling £3,316.
which one has the biggest size
  • Expected QueryRecordComparator to be Biggest but found None
  • Expected to find entity 'comparator' but found only {unknown_entity, text, date_in, date_mod, datetime}
  • Response: I'm afraid I didn't quite get all of that, however since 5th June 2019 your outgoings were nine payments totalling £3,316.
which of those came through most recently
  • Expected QueryRecordComparator to be Latest but found None
  • Expected {comparator} to have single value 'latest' but found 'most'
  • Response: Hang on - I didn't quite understand all that, however since 5th June 2019 your outgoings were nine payments totalling £3,316.
which of those is the most current
  • Expected QueryRecordComparator to be Latest but found None
  • Expected {comparator} to have single value 'latest' but found 'most'
  • Response: I didn't understand all of that, however since 5th June 2019 your outgoings were nine payments totalling £3,316.
which of those is the most up-to-date
  • Expected QueryRecordComparator to be Latest but found None
  • Expected to find entity 'comparator' but found only {unknown_entity, text, date_in, date_mod, datetime}
  • Response: I'm sorry but I didn't understand all of that, however since 5th June 2019 your expenditure was nine payments totalling £3,316.
which of those was sent most recently
  • Expected QueryRecordComparator to be Latest but found None
  • Expected {comparator} to have single value 'latest' but found 'most'
  • Response: I'm afraid I didn't quite get all of that, however since 5th June 2019 your spending was nine payments totalling £3,316.
what one is of the least significant size
  • Expected QueryRecordComparator to be Smallest but found None
  • Expected to find entity 'comparator' but found only {unknown_entity, text, date_in, date_mod, datetime}
  • Response: I didn't understand all of that, however since 5th June 2019 your outgoings were nine payments totalling £3,316.
SME-Issues commented 5 years ago

Test Exception

Expressions Notes
and which of those got paid in the end SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Did not find any known datetime values in 'and which of those got paid in the end' - found datetime : end at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase…
were they paid in the end SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Did not find any known datetime values in 'were they paid in the end' - found datetime : end at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpre…
which ones got paid in the end SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Did not find any known datetime values in 'which ones got paid in the end' - found datetime : end at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .Process…
I know, but what about on monday SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Laas error: IndexError('list index out of range',)
56 at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters te…
Next Show Me Whats The Smallest SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Multiple comparator values in text 'next show me what is the smallest' at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpres…
I'm interested in seeing Gibson Ltd SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Multiple pay_from values found . at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters testParameters) in D:/a/…
that's ok but what about Gibson Ltd SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Response text is empty at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters testParameters) in D:/a/1/s/src/A…
which is the most recent SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Response text is empty at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters testParameters) in D:/a/1/s/src/A…
which one is the most large SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Response text is empty at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters testParameters) in D:/a/1/s/src/A…
what if we add Saturday into the mix SMEBankingAPI .Tests .Reporting .Helpers .TestFailedException: Error running test: Unsupported intent: 'query_acct' at async Task SMEBankingAPI .Tests .Reporting .InputProcessing .BankingAiProcessingTestBase .ProcessExpression(TestSingleExpressionParameters testParameters) in D:/a…